diff options
author | Jeff King <peff@peff.net> | 2009-01-29 00:56:34 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2009-01-28 23:40:53 -0800 |
commit | 915308b187bdaba9ad1c6c3dea7b2b4b200b4796 (patch) | |
tree | c04697728ff54f8ee2fa8fdcdd4d92b258c7df20 /commit.c | |
parent | test-path-utils: Fix off by one, found by valgrind (diff) | |
download | tgif-915308b187bdaba9ad1c6c3dea7b2b4b200b4796.tar.xz |
avoid 31-bit truncation in write_loose_object
The size of the content we are adding may be larger than
2.1G (i.e., "git add gigantic-file"). Most of the code-path
to do so uses size_t or unsigned long to record the size,
but write_loose_object uses a signed int.
On platforms where "int" is 32-bits (which includes x86_64
Linux platforms), we end up passing malloc a negative size.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions