From: Al Viro <viro@ZenIV.linux.org.uk>
To: Doug Nazar <nazard.lkml@gmail.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"J. Bruce Fields" <bfields@citi.umich.edu>,
pNFS Mailing List <pnfs@linux-nfs.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last()
Date: Wed, 24 Mar 2010 18:56:04 +0000 [thread overview]
Message-ID: <20100324185604.GT30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4BAA5955.4000001@gmail.com>
On Wed, Mar 24, 2010 at 02:26:29PM -0400, Doug Nazar wrote:
> I also see it....didn't bisect it yet since I was in a rush and had
> a simple work around. I was doing a git pull between two
> repositories on a NFS 4 w/krb5 security. Got the error about
> .git/objects/pack (error: unable to open object pack directory:
> .git/objects/pack: Is a directory). If I then run 'ls
> .git/objects/pack', and then the 'git pull' again it works.
Very interesting... The damn thing *is* a directory, which should have
made NFS skip all lookup_instantiate_filp() tricks completely. IOW, it's
not hitting anything intent-related at that case.
I really wonder where the hell does EISDIR come from; no matter how screwed
the cached attributes are, there's not a lot of places where we can return
that sucker. It either comes from something in NFS itself, or it's
may_open() getting MAY_WRITE on that object or it has to see O_CREAT in
open_flag. And acc_mode is not modified after it's set in do_filp_open().
If that calculation (acc_mode by open_flag) would be buggered for O_RDONLY,
we'd be seeing a lot more breakage, starting with ls(1) ;-)
One possibility is that shit hits the fan a bit earlier and git really passes
something odd to that open() as the result of bogus stat(), etc.
Folks, could you try the following: in do_last() move case LAST_DOT:
to immediately after follow_dotdot(nd); and see if that changes anything?
It shouldn't, but if nfs is playing odd tricks with ->d_revalidate() for
directories acting differently depending on LOOKUP_PARENT in flags...
IOW, replace
case LAST_DOTDOT:
follow_dotdot(nd);
dir = nd->path.dentry;
if (nd->path.mnt->mnt_sb->s_type->fs_flags & FS_REVAL_DOT) {
if (!dir->d_op->d_revalidate(dir, nd)) {
error = -ESTALE;
goto exit;
}
}
/* fallthrough */
case LAST_DOT:
case LAST_ROOT:
with
case LAST_DOTDOT:
follow_dotdot(nd);
/* fallthrough */
case LAST_DOT:
dir = nd->path.dentry;
if (nd->path.mnt->mnt_sb->s_type->fs_flags & FS_REVAL_DOT) {
if (!dir->d_op->d_revalidate(dir, nd)) {
error = -ESTALE;
goto exit;
}
}
/* fallthrough */
case LAST_ROOT:
and see what'll change.
next prev parent reply other threads:[~2010-03-24 18:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:49 [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last() Boaz Harrosh
2010-03-24 15:49 ` Boaz Harrosh
2010-03-24 16:00 ` Al Viro
2010-03-24 16:04 ` Boaz Harrosh
2010-03-24 16:07 ` Al Viro
2010-03-24 16:10 ` Boaz Harrosh
2010-03-24 16:39 ` Al Viro
2010-03-24 17:15 ` Boaz Harrosh
2010-03-24 17:32 ` [pnfs] " Boaz Harrosh
2010-03-24 17:47 ` Boaz Harrosh
2010-03-24 17:58 ` Boaz Harrosh
2010-03-24 18:06 ` Al Viro
2010-03-24 18:26 ` Doug Nazar
2010-03-24 18:56 ` Al Viro [this message]
2010-03-25 9:39 ` Boaz Harrosh
2010-03-25 10:12 ` Al Viro
2010-03-25 10:22 ` Benny Halevy
2010-03-25 10:31 ` Benny Halevy
2010-03-25 10:49 ` Al Viro
2010-03-25 10:56 ` Benny Halevy
2010-03-25 11:00 ` Al Viro
2010-03-25 11:12 ` Benny Halevy
2010-03-25 11:13 ` Benny Halevy
2010-03-25 11:55 ` Al Viro
2010-03-25 13:00 ` Boaz Harrosh
2010-03-25 13:11 ` Boaz Harrosh
2010-03-25 10:54 ` Al Viro
2010-03-25 11:19 ` Benny Halevy
2010-03-25 12:07 ` Benny Halevy
2010-03-25 12:18 ` Benny Halevy
2010-03-25 13:06 ` Al Viro
2010-03-25 13:30 ` Boaz Harrosh
2010-03-25 13:37 ` Al Viro
2010-03-25 13:45 ` Boaz Harrosh
2010-03-25 14:04 ` Al Viro
2010-03-25 14:27 ` Boaz Harrosh
2010-03-25 15:25 ` Al Viro
2010-03-25 17:28 ` Boaz Harrosh
2010-03-25 17:59 ` Trond Myklebust
2010-03-25 18:06 ` Boaz Harrosh
2010-03-25 18:18 ` Trond Myklebust
2010-03-25 18:33 ` Boaz Harrosh
2010-03-25 13:52 ` Benny Halevy
2010-03-25 14:06 ` Al Viro
2010-03-25 14:07 ` Benny Halevy
2010-03-25 14:36 ` Benny Halevy
2010-03-24 18:02 ` Trond Myklebust
2010-03-24 18:10 ` Trond Myklebust
2010-03-25 9:13 ` Boaz Harrosh
2010-03-25 15:44 ` Trond Myklebust
2010-03-25 10:11 ` Benny Halevy
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=20100324185604.GT30031@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bfields@citi.umich.edu \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nazard.lkml@gmail.com \
--cc=pnfs@linux-nfs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.