summaryrefslogtreecommitdiff
path: root/lockfile.c
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-01-04 07:09:08 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-01-05 06:17:59 (GMT)
commit8977c110b5bbd230c28c727ddb85856067d55cfb (patch)
tree99c23def7dd3a9279226614f3af0aba82a555c81 /lockfile.c
parent1084b845d9d77bcb2e8255636358dd0dc35360a5 (diff)
downloadgit-8977c110b5bbd230c28c727ddb85856067d55cfb.zip
git-8977c110b5bbd230c28c727ddb85856067d55cfb.tar.gz
git-8977c110b5bbd230c28c727ddb85856067d55cfb.tar.bz2
pack-check.c::verify_packfile(): don't run SHA-1 update on huge datav1.4.4.4
Running the SHA1_Update() on the whole packfile in a single call revealed an overflow problem we had in the SHA-1 implementation on POWER architecture some time ago, which was fixed with commit b47f509b (June 19, 2006). Other SHA-1 implementations may have a similar problem. The sliding mmap() series already makes chunked calls to SHA1_Update(), so this patch itself will become moot when it graduates to "master", but in the meantime, run the hash function in smaller chunks to prevent possible future problems. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'lockfile.c')
0 files changed, 0 insertions, 0 deletions