From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Nicolas Pitre <nico@fluxnic.net>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] recover from "failed to apply delta"
Date: Fri, 14 Jun 2013 14:51:35 -0700 [thread overview]
Message-ID: <7vsj0kmkd4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130614214943.GA29138@sigill.intra.peff.net> (Jeff King's message of "Fri, 14 Jun 2013 17:49:44 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, Jun 13, 2013 at 08:05:21PM -0400, Nicolas Pitre wrote:
>
>> > We already handle the case where we were not able to read
>> > the delta from disk. However, when we find that the delta we
>> > read does not apply, we simply die. This case is harder to
>> > trigger, as corruption in the delta data itself would
>> > trigger a crc error from zlib. However, a corruption that
>> > pointed us at the wrong delta base might cause it.
>>
>> That makes sense.
>>
>> Could you produce a test case to go along with this change?
>
> Yes. I was a little worried I would have trouble doing it without
> relying on a lot of pack internals, but the infrastructure you set up in
> t5303 makes it relatively easy (and we do not have to make any
> assumptions that t5303 does not already make).
>
> Here is a re-roll; the first patch is a small cleanup in t5303 that is
> required for the new tests to work.
Heh, I was doing the same, but I cheated ;-)
diff --git a/t/t5303-pack-corruption-resilience.sh b/t/t5303-pack-corruption-resilience.sh
index 5b1250f..57436db 100755
--- a/t/t5303-pack-corruption-resilience.sh
+++ b/t/t5303-pack-corruption-resilience.sh
@@ -51,7 +51,7 @@ do_corrupt_object() {
ofs=`git show-index < ${pack}.idx | grep $1 | cut -f1 -d" "` &&
ofs=$(($ofs + $2)) &&
chmod +w ${pack}.pack &&
- dd of=${pack}.pack count=1 bs=1 conv=notrunc seek=$ofs &&
+ dd of=${pack}.pack count=${3-1} bs=1 conv=notrunc seek=$ofs &&
test_must_fail git verify-pack ${pack}.pack
}
@@ -276,6 +276,30 @@ test_expect_success \
git cat-file blob $blob_3 > /dev/null'
test_expect_success \
+ 'corrupt delta-part of a packed object, fall back to loose' \
+ 'create_new_pack &&
+ path=$(echo "$blob_3" | sed -e "s|^\(..\)|\1/|") &&
+ cat ".git/objects/$path" >saved &&
+ git prune-packed &&
+
+ dd if=${pack}.idx bs=1 count=20 skip=1032 >blob1-bin &&
+ dd if=${pack}.pack bs=1 count=20 skip=2233 >blob3-delta-base-bin &&
+
+ # At the beginning of the REF_DELTA representation of $blob_3,
+ # write 20-byte base object name for $blob_1, instead of $blob_2.
+ # The binary representation of object name for $blob_1 is found
+ # at offset 4 + 4 + 256*4 = 1032 for 20 bytes.
+ dd if=${pack}.idx bs=1 count=20 skip=1032 | do_corrupt_object $blob_3 2 20 &&
+ test_must_fail git cat-file blob $blob_3 >/dev/null &&
+
+ # Resurrect the loose object for $blob_3
+ mkdir -p .git/objects/$(echo "$path" | sed -e "s|^\(..\).*|\1|") &&
+ cat saved >".git/objects/$path" &&
+
+ git cat-file blob $blob_3 >/dev/null
+'
+
+test_expect_success \
'corrupting header to have too small output buffer fails unpack' \
'create_new_pack &&
git prune-packed &&
next prev parent reply other threads:[~2013-06-14 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 23:26 [PATCH] unpack_entry: do not die when we fail to apply a delta Jeff King
2013-06-14 0:05 ` Nicolas Pitre
2013-06-14 21:49 ` [PATCH 0/2] recover from "failed to apply delta" Jeff King
2013-06-14 21:51 ` [PATCH 1/2] t5303: drop "count=1" from corruption dd Jeff King
2013-06-14 21:51 ` Junio C Hamano [this message]
2013-06-14 21:56 ` [PATCH 0/2] recover from "failed to apply delta" Jeff King
2013-06-14 22:23 ` Junio C Hamano
2013-06-14 21:53 ` [PATCH 2/2] unpack_entry: do not die when we fail to apply a delta Jeff King
2013-06-14 21:59 ` Junio C Hamano
2013-06-14 22:19 ` Jeff King
2013-06-14 14:53 ` [PATCH] " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vsj0kmkd4.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).