Anonymous committed 25f3af3

Correctly report corrupted objects

The errno check added in commit 3ba7a06 "A loose object is not corrupt
if it cannot be read due to EMFILE" only checked for whether errno is
not ENOENT and thus incorrectly treated "no error" as an error

Because of that, it never reached the code path that would report that
the object is corrupted and instead caused funny errors like:

fatal: failed to read object 333c4768ce595793fdab1ef3a036413e2a883853: Success

So we have to extend the check to cover the case in which the object
file was successfully read, but its contents are corrupted.

Reported-by: Will Palmer <>
Signed-off-by: Björn Steinbrink <>
Signed-off-by: Junio C Hamano <>

  • Participants
  • Parent commits b20e9b0

Comments (0)

Files changed (1)

 		return data;
-	if (errno != ENOENT)
+	if (errno && errno != ENOENT)
 		die_errno("failed to read object %s", sha1_to_hex(sha1));
 	/* die if we replaced an object with one that does not exist */