From: Ian Kent <raven@themaw.net>
To: "McIntyre, Vincent (CASS, Marsfield)" <Vincent.Mcintyre@csiro.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
autofs mailing list <autofs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] vfs: check for autofs expiring dentry in follow_automount()
Date: Tue, 31 Mar 2020 08:22:19 +0800 [thread overview]
Message-ID: <546b7365be9c6315d93464af10fc97d453f39784.camel@themaw.net> (raw)
In-Reply-To: <20200330232032.vmlt3glzqdkgijhy@mayhem.atnf.CSIRO.AU>
On Mon, 2020-03-30 at 23:20 +0000, McIntyre, Vincent (CASS, Marsfield)
wrote:
> On Tue, Mar 31, 2020 at 07:07:02AM +0800, Ian Kent wrote:
> > follow_automount() checks if a stat family system call path walk is
> > being done on a positive dentry and and returns -EISDIR to indicate
> > the dentry should be used as is without attempting an automount.
> >
> > But if autofs is expiring the dentry at the time it should be
> > remounted following the expire.
> >
> > There are two cases, in the case of a "nobrowse" indirect autofs
> > mount it would have been mounted on lookup anyway. In the case of
> > a "browse" indirect or direct autofs mount re-mounting it will
> > maintain the mount which is what user space would be expected.
> >
> > This will defer expiration of the mount which might lead to mounts
> > unexpectedly remaining mounted under heavy stat activity but
> > there's
> > no other choice in order to maintain consistency for user space.
> >
> > Signed-off-by: Ian Kent <raven@themaw.net>
> > ---
> > fs/autofs/root.c | 10 +++++++++-
> > fs/namei.c | 13 +++++++++++--
> > 2 files changed, 20 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/autofs/root.c b/fs/autofs/root.c
> > index a1c9c32e104f..b3f748e4df08 100644
> > --- a/fs/autofs/root.c
> > +++ b/fs/autofs/root.c
> > @@ -406,9 +406,17 @@ static int autofs_d_manage(const struct path
> > *path, bool rcu_walk)
> >
> > /* Check for (possible) pending expire */
> > if (ino->flags & AUTOFS_INF_WANT_EXPIRE) {
> > + /* dentry possibly going to be picked for expire,
> > + * proceed to ref-walk mode.
> > + */
> > if (rcu_walk)
> > return -ECHILD;
> > - return 0;
> > +
> > + /* ref-walk mode, return 1 so follow_automount()
> > + * can wait on the expire outcome and possibly
> > + * attempt a re-mount.
> > + */
> > + return 1;
> > }
> >
> > /*
> > diff --git a/fs/namei.c b/fs/namei.c
> > index db6565c99825..869e0d4bb4d9 100644
> > --- a/fs/namei.c
> > +++ b/fs/namei.c
> > @@ -1227,11 +1227,20 @@ static int follow_automount(struct path
> > *path, struct nameidata *nd,
> > * mounted directory. Also, autofs may mark negative dentries
> > * as being automount points. These will need the attentions
> > * of the daemon to instantiate them before they can be used.
> > + *
> > + * Also if ->d_manage() returns 1 the dentry transit needs
> > + * to be managing. For autofs, a return of 1 it tells us the
>
> Unclear. Do you mean "to be managed." ? Or "managing." ?
Right, and I didn't label these v2 either, bit stressed at the
moment I guess.
Ian
>
> Cheers
> Vince
>
> > + * dentry might be expired, so proceed to ->d_automount().
> > */
> > if (!(nd->flags & (LOOKUP_PARENT | LOOKUP_DIRECTORY |
> > LOOKUP_OPEN | LOOKUP_CREATE |
> > LOOKUP_AUTOMOUNT)) &&
> > - path->dentry->d_inode)
> > - return -EISDIR;
> > + path->dentry->d_inode) {
> > + if (path->dentry->d_flags & DCACHE_MANAGE_TRANSIT) {
> > + if (!path->dentry->d_op->d_manage(path, false))
> > + return -EISDIR;
> > + } else
> > + return -EISDIR;
> > + }
> >
> > nd->total_link_count++;
> > if (nd->total_link_count >= 40)
> >
>
> --
next prev parent reply other threads:[~2020-03-31 0:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 23:06 [PATCH 1/4] autofs: dont call do_expire_wait() in autofs_d_manage() Ian Kent
2020-03-30 23:06 ` [PATCH 2/4] autofs: remove rcu_walk parameter from autofs_expire_wait() Ian Kent
2020-03-30 23:07 ` [PATCH 3/4] vfs: check for autofs expiring dentry in follow_automount() Ian Kent
2020-03-30 23:20 ` McIntyre, Vincent (CASS, Marsfield)
2020-03-31 0:22 ` Ian Kent [this message]
2020-03-30 23:07 ` [PATCH 4/4] autofs: add comment about autofs_mountpoint_changed() Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2020-03-26 5:23 [PATCH 1/4] autofs: dont call do_expire_wait() in autofs_d_manage() Ian Kent
2020-03-26 5:23 ` [PATCH 3/4] vfs: check for autofs expiring dentry in follow_automount() Ian Kent
2020-03-27 5:18 ` McIntyre, Vincent (CASS, Marsfield)
2020-03-27 11:31 ` Ian Kent
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=546b7365be9c6315d93464af10fc97d453f39784.camel@themaw.net \
--to=raven@themaw.net \
--cc=Vincent.Mcintyre@csiro.au \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).