From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Farhan Khan <khanzf@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Calculate packfile and idxfile checksums
Date: Fri, 18 Jan 2019 09:36:54 +0100 [thread overview]
Message-ID: <87lg3i4b15.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CAFd4kYAbrUcV2U1u6Fz3VgZDN_YcpLrSymeA5bvvLy1LY98aHA@mail.gmail.com>
On Fri, Jan 18 2019, Farhan Khan wrote:
> Hi all,
>
> I am trying to understand how git's index-pack works, particularly how
> it calculates the packfile checksum and idxfile checksum.
It's unclear if this is what you're asking, but the pack checksum is
just a 20 bytes of SHA1 of the preceding contents at the end for *.idx
and *.pack. As seen with this program:
$ perl -MFile::Slurp=slurp -MDigest::SHA=sha1 -wE 'my $f = shift; my $c = slurp($f); my $cp = $c; $cp =~ s/.{20}$//s; my $n = $cp . sha1($cp); if ($n eq $c) { say "Computed checksum trailer for $f" } else { say "Failed trailer for new content for $f is different" }' pack-79c2ccce950e6676452dc9f0473f80003e7ccdef.idx
Computed checksum trailer for pack-79c2ccce950e6676452dc9f0473f80003e7ccdef.idx
You can also feed it *.pack files.
> I traced back the packfile checksum in the source to the value char
> *sha1 that is utilized in write_idx_file() in pack_file.c:45. However,
> I cannot
It seems you mean pack-write.c not pack_file.c
> determine where this value is set.
It's initialized in cmd_index_pack() and then passed down to that
function.
> My printf() debugging has it set at pack-write.c:171 (right before the
> hashwrite call) but it does not seem to be utilized prior to that
> point. Please assist.
I'm happy to help, but still not quite sure what the source of the
confusion is, maybe that the variable in index-pack.c has a different
name and is passed down to pack-write.c's function as a pointer?
next prev parent reply other threads:[~2019-01-18 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 7:24 Calculate packfile and idxfile checksums Farhan Khan
2019-01-18 8:36 ` Ævar Arnfjörð Bjarmason [this message]
2019-01-18 23:51 ` Farhan Khan
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=87lg3i4b15.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=khanzf@gmail.com \
/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).