summaryrefslogtreecommitdiff
path: root/t/t4100
diff options
context:
space:
mode:
authorLibravatar Shawn O. Pearce <spearce@spearce.org>2009-10-14 07:23:51 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-10-14 13:39:37 -0700
commitb3118bdc91876cbc04b7e81dcf7bea71d86ce4f8 (patch)
treeaa1b183bcec0f4057addaad2ad5f437e13540622 /t/t4100
parentchange throughput display units with fast links (diff)
downloadtgif-b3118bdc91876cbc04b7e81dcf7bea71d86ce4f8.tar.xz
sha1_file: Fix infinite loop when pack is corrupted
Some types of corruption to a pack may confuse the deflate stream which stores an object. In Andy's reported case a 36 byte region of the pack was overwritten, leading to what appeared to be a valid deflate stream that was trying to produce a result larger than our allocated output buffer could accept. Z_BUF_ERROR is returned from inflate() if either the input buffer needs more input bytes, or the output buffer has run out of space. Previously we only considered the former case, as it meant we needed to move the stream's input buffer to the next window in the pack. We now abort the loop if inflate() returns Z_BUF_ERROR without consuming the entire input buffer it was given, or has filled the entire output buffer but has not yet returned Z_STREAM_END. Either state is a clear indicator that this loop is not working as expected, and should not continue. This problem cannot occur with loose objects as we open the entire loose object as a single buffer and treat Z_BUF_ERROR as an error. Reported-by: Andy Isaacson <adi@hexapodia.org> Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Acked-by: Nicolas Pitre <nico@fluxnic.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4100')
0 files changed, 0 insertions, 0 deletions