git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Calculating pack file SHA value

From
Farhan Khan <farhan@farhan.codes>
Date
Mar 28, 2019, 01:06 UTC
Message-ID
<a48b86698802006045ed0af060b4e822@farhan.codes>
Hi all,

I am trying to figure out how to calculate the SHA value of a pack file when you run `git index-pack file.pack`. I am close, but having a bit of trouble at the end. Here's my understanding so far.

Git buffers data to be processed and when its exhausted, updates the SHA checksum with the previously read data. This is from builtin/index-pack.c, specifically fill() which calls flush() to update the SHA value. My question is, how does git determine how many bytes at a time to process?

The size of the buffer is the file-scope variable input_len. This size seems to be 4096 several times until the very end where it reduces to less-than 4096 (obviously this depends on the pack file, but in my case its 1074 bytes). Ordinarily I would think its a result of the read() call not receiving the full 4096 bytes, but there still are left over bytes in the file but my manual verification shows there are still remaining bytes in the file which are not run through the SHA checksum.

How does git calculate a pack file's SHA verification? How does it know what size (number of bytes) to read when running flush() to update the buffer? (typically 4096). How does it know when in the file to stop updating the SHA1 value?

I hope my questions are clear. Thanks!

--- Farhan Khan PGP Fingerprint: 1312 89CE 663E 1EB2 179C 1C83 C41D 2281 F8DA C0DE

Next: Jeff King
Message 1 of 2 in “Calculating pack file SHA value”
  1. Farhan KhanMar 28, 2019
  2. Jeff KingMar 28, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.