From: Shawn Pearce <spearce@spearce.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Error writing loose object on Cygwin
Date: Wed, 12 Jul 2006 01:00:16 -0400 [thread overview]
Message-ID: <20060712050016.GA8002@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0607112132540.5623@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
> On Tue, 11 Jul 2006, Junio C Hamano wrote:
>
> > Shawn Pearce <spearce@spearce.org> writes:
> >
> > > Has anyone else seen this type of behavior before? Any suggestions
> > > on debugging this issue?
> >
> > I would suggest raising this (politely) to Cygwin people.
>
> Well, since it apparently works with W2000, and breaks with XP, I suspect
> it's actually Windows that just returns the wrong error code.
>
> It's entirely possible that we should just make that whole
>
> if (ret == ENOENT)
>
> go away. Yes, it's the right error code if a subdirectory is missing, and
> yes, POSIX requires it, and yes, WXP is probably just a horrible piece of
> sh*t, but on the other hand, I don't think git really has any serious
> reason to even care.
>
> So we might as well say that if the link() fails for _any_ reason, we'll
> try to see if doing the mkdir() and re-trying the link helps.
Hmm. Its a single mkdir call before we give up and tell the user
something is wrong. The following change appears to work OK here on
a reasonably POSIX compliant system (OK meaning it reports errors reasonably).
Given that this type of error (failed link) shouldn't happen
that often, except for on Coda or FAT (according to a comment in
move_temp_to_file), I guess the change is OK and comes with little
penalty. But for Coda and FAT users things are going to slow down a
little bit as we try mkdir for every new loose object being created
before we try rename.
Tomorrow when I get access to my Cygwin system again I'll try to
write up a tiny test case which shows the error behavior we are
seeing and send it to the Cygwin mailing list, as this really does
seem to be a Cygwin or Windows issue. But of course having GIT
handle this case slightly better wouldn't be bad either. :-)
diff --git a/sha1_file.c b/sha1_file.c
index 8734d50..db4bddc 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -1336,26 +1336,23 @@ static int link_temp_to_file(const char
return 0;
/*
- * Try to mkdir the last path component if that failed
- * with an ENOENT.
+ * Try to mkdir the last path component if that failed.
*
* Re-try the "link()" regardless of whether the mkdir
* succeeds, since a race might mean that somebody
* else succeeded.
*/
ret = errno;
- if (ret == ENOENT) {
- char *dir = strrchr(filename, '/');
- if (dir) {
- *dir = 0;
- mkdir(filename, 0777);
- if (adjust_shared_perm(filename))
- return -2;
- *dir = '/';
- if (!link(tmpfile, filename))
- return 0;
- ret = errno;
- }
+ char *dir = strrchr(filename, '/');
+ if (dir) {
+ *dir = 0;
+ mkdir(filename, 0777);
+ if (adjust_shared_perm(filename))
+ return -2;
+ *dir = '/';
+ if (!link(tmpfile, filename))
+ return 0;
+ ret = errno;
}
return ret;
}
next prev parent reply other threads:[~2006-07-12 5:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 3:57 Error writing loose object on Cygwin Shawn Pearce
2006-07-12 4:15 ` Junio C Hamano
2006-07-12 4:36 ` Linus Torvalds
2006-07-12 5:00 ` Shawn Pearce [this message]
2006-07-13 4:27 ` Junio C Hamano
2006-07-13 5:51 ` Christopher Faylor
2006-07-14 3:34 ` Shawn Pearce
2006-07-14 5:24 ` Christopher Faylor
2006-07-14 5:26 ` Linus Torvalds
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=20060712050016.GA8002@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).