summaryrefslogtreecommitdiff
path: root/t/t4036-format-patch-signer-mime.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2020-11-13 00:07:17 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-11-16 13:41:35 -0800
commit9bb4542b8c1b91189126cf0fc42e2689fc9224c6 (patch)
tree55fd470c723203f246016f91266e6365f38af94b /t/t4036-format-patch-signer-mime.sh
parentfsck: correctly compute checksums on idx files larger than 4GB (diff)
downloadtgif-9bb4542b8c1b91189126cf0fc42e2689fc9224c6.tar.xz
block-sha1: take a size_t length parameter
The block-sha1 implementation takes an "unsigned long" for the length of a buffer to hash, but our hash algorithm wrappers take a size_t, as do other implementations we support like openssl or sha1dc. On many systems, including Linux, these two are equivalent, but they are not on Windows (where only a "long long" is 64 bits). As a result, passing large chunks to a single the_hash_algo->update_fn() would produce wrong answers there. Note that we don't need to update any other sizes outside of the function interface. We store the cumulative size in a "long long" (which we must do since we hash things bigger than 4GB, like packfiles, even on 32-bit platforms). And internally, we break that size_t len down into 64-byte blocks to feed into the guts of the algorithm. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4036-format-patch-signer-mime.sh')
0 files changed, 0 insertions, 0 deletions