From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 2/2] A loose object is not corrupt if it cannot be read due to EMFILE
Date: Thu, 28 Oct 2010 13:53:30 -0700 [thread overview]
Message-ID: <1288299210-27092-2-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1288299210-27092-1-git-send-email-gitster@pobox.com>
"git fsck" bails out with a claim that a loose object that cannot be
read but exists on the filesystem to be corrupt, which is wrong when
read_object() failed due to e.g. EMFILE.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
sha1_file.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 5ed5497..f709ed6 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -2090,16 +2090,21 @@ void *read_sha1_file_repl(const unsigned char *sha1,
const unsigned char **replacement)
{
const unsigned char *repl = lookup_replace_object(sha1);
- void *data = read_object(repl, type, size);
+ void *data;
char *path;
const struct packed_git *p;
+ errno = 0;
+ data = read_object(repl, type, size);
if (data) {
if (replacement)
*replacement = repl;
return data;
}
+ if (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 */
if (repl != sha1)
die("replacement %s not found for %s",
--
1.7.3.2.191.g2d0e57
next prev parent reply other threads:[~2010-10-28 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 20:53 [PATCH 1/2] read_sha1_file(): report correct name of packfile with a corrupt object Junio C Hamano
2010-10-28 20:53 ` Junio C Hamano [this message]
2010-11-18 14:19 ` [PATCH 2/2] A loose object is not corrupt if it cannot be read due to EMFILE Erik Faye-Lund
2010-11-18 16:43 ` Johannes Sixt
2010-11-18 17:21 ` Erik Faye-Lund
2010-11-18 17:29 ` Jonathan Nieder
2010-11-18 18:18 ` Erik Faye-Lund
2010-11-18 18:23 ` Casey Dahlin
2010-11-18 20:27 ` Jonathan Nieder
2010-10-29 8:08 ` [PATCH 1/2] read_sha1_file(): report correct name of packfile with a corrupt object Johannes Sixt
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=1288299210-27092-2-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).