From: Jeff Layton <jlayton@redhat.com>
To: NeilBrown <neilb@suse.com>, Ian Kent <ikent@redhat.com>,
Latchesar Ionkov <lucho@ionkov.net>,
Eric Van Hensbergen <ericvh@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Ron Minnich <rminnich@sandia.gov>,
Trond Myklebust <trondmy@primarydata.com>
Cc: linux-nfs@vger.kernel.org, autofs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/3] VFS: name lookup improvements.
Date: Thu, 09 Nov 2017 07:32:34 -0500 [thread overview]
Message-ID: <1510230754.29194.6.camel@redhat.com> (raw)
In-Reply-To: <151021179901.22743.15252956909042161062.stgit@noble>
On Thu, 2017-11-09 at 18:20 +1100, NeilBrown wrote:
> These three patches address two issues: d_weak_revalidate and
> path_mountpoint lookups.
>
> The former is poorly defined and doesn't actually do the one thing
> that it would be useful for it to do. So the nfs implemention
> is improved, the 9p one discarded, and the documentation clarified.
>
> Given this change and recent change to follow_automount() the
> mountpoint path lookup functions are no longer needed. The regular
> path look functions are quite sufficient.
> The second two patches remove this with detailed explanation of why
> it is OK.
>
> Thanks,
> NeilBrown
>
>
> ---
>
> NeilBrown (3):
> VFS/nfs/9p: revise meaning of d_weak_invalidate.
> VFS: remove user_path_mountpoint_at()
> VFS / autofs4: remove kern_path_mountpoint()
>
>
> Documentation/filesystems/porting | 5 +
> Documentation/filesystems/vfs.txt | 11 +--
> fs/9p/vfs_dentry.c | 1
> fs/autofs4/dev-ioctl.c | 5 -
> fs/internal.h | 1
> fs/namei.c | 150 -------------------------------------
> fs/namespace.c | 2
> fs/nfs/dir.c | 60 ++-------------
> include/linux/namei.h | 1
> 9 files changed, 24 insertions(+), 212 deletions(-)
>
> --
> Signature
>
I love that diffstat and I think the patches and the logic behind them
look reasonable. I'm the one that added d_weak_revalidate and while it
did fix a problem at the time, it has always seemed a bit of an odd
d_op.
Your patch does make me wonder if we should consider merging
d_weak_revalidate and d_revalidate back together, and simply require all
the d_revalidate ops vet the flags more thoroughly.
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2017-11-09 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 7:20 [PATCH 0/3] VFS: name lookup improvements NeilBrown
2017-11-09 7:20 ` [PATCH 3/3] VFS / autofs4: remove kern_path_mountpoint() NeilBrown
2017-11-09 20:06 ` Linus Torvalds
2017-11-09 7:20 ` [PATCH 2/3] VFS: remove user_path_mountpoint_at() NeilBrown
2017-11-09 7:20 ` [PATCH 1/3] VFS/nfs/9p: revise meaning of d_weak_invalidate NeilBrown
2017-11-09 12:32 ` Jeff Layton [this message]
2017-11-09 21:06 ` [PATCH 0/3] VFS: name lookup improvements NeilBrown
2017-11-10 0:21 ` NeilBrown
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=1510230754.29194.6.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=autofs@vger.kernel.org \
--cc=ericvh@gmail.com \
--cc=ikent@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=neilb@suse.com \
--cc=rminnich@sandia.gov \
--cc=torvalds@linux-foundation.org \
--cc=trondmy@primarydata.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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).