From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@infradead.org
Subject: Re: [PATCH 5/6] vfs: reorganize do_lookup
Date: Wed, 4 Apr 2012 04:16:29 +0100 [thread overview]
Message-ID: <20120404031629.GB6589@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87hax1s069.fsf@tucsk.pomaz.szeredi.hu>
On Tue, Apr 03, 2012 at 10:13:18AM +0200, Miklos Szeredi wrote:
> The do_last() reorganization in the atomic-open series needs to be split
> up, I realize. Do you have any other high level comments about that
> series?
Yes.
a) Please, pull removal of open-from-d_revalidate() as far in front
of the queue as possible, *along* *with* -EOPENSTALE stuff. Without the
latter the former is simply broken - we might have hit -ESTALE before and
LOOKUP_REVAL might have already been set, so just failing ->open() with
ESTALE may end up not repeating it.
TBH, had that thing been in front of the queue, I would've put
it into the last pull request; that particular idiocy (NFS4 doing open
from all methods involved, except for ->open()) had been a serious source
of annoyance for a long time. It really needs killing...
b) opendata is simply bogus. You need to pass caller-allocated
struct file in any case, right? So why not use it to pass what you
need to pass? We want to be able to tell "it's a symlink, here's the
vfsmount/dentry, now sod off and handle it yourself"? Sure, but struct
file *already* contains struct path and that's not something that might
disappear on future kernel changes ;-)
next prev parent reply other threads:[~2012-04-04 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 10:54 [PATCH 0/6] vfs: path lookup fixes and cleanups Miklos Szeredi
2012-03-26 10:54 ` [PATCH 1/6] vfs: fix d_need_lookup/d_revalidate order in do_lookup Miklos Szeredi
2012-03-26 10:54 ` [PATCH 2/6] vfs: don't revalidate just looked up dentry Miklos Szeredi
2012-03-26 10:54 ` [PATCH 3/6] vfs: move MAY_EXEC check from __lookup_hash() Miklos Szeredi
2012-03-26 10:54 ` [PATCH 4/6] vfs: set LOOKUP_JUMPED in follow_managed Miklos Szeredi
2012-03-30 2:39 ` Al Viro
2012-03-26 10:54 ` [PATCH 5/6] vfs: reorganize do_lookup Miklos Szeredi
2012-03-30 19:05 ` Al Viro
2012-04-03 8:13 ` Miklos Szeredi
2012-04-04 3:16 ` Al Viro [this message]
2012-04-05 14:44 ` Miklos Szeredi
2012-03-26 10:54 ` [PATCH 6/6] vfs: split __lookup_hash Miklos Szeredi
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=20120404031629.GB6589@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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