From: Andrew Morton <akpm@linux-foundation.org>
To: Ian Kent <raven@themaw.net>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] autofs - fix fix symlinks arent checked for expiry
Date: Thu, 26 Dec 2013 13:42:53 -0800 [thread overview]
Message-ID: <20131226134253.5f4b2f02a00e11b8de49770e@linux-foundation.org> (raw)
In-Reply-To: <20131224094459.20051.4889.stgit@perseus.fritz.box>
On Tue, 24 Dec 2013 17:44:59 +0800 Ian Kent <raven@themaw.net> wrote:
> When following a symlink the last_used counter is unconditionally
> updated causing the expire checks from user space to prevent
> expiry. Opps!
A bit unclear. You're saying that userspace's act of checking expiry
status will itself disrupt the expiry process?
Also, it's rather unclear what the userspace impact is here, and how
severe it is. Please always carefully describe the user-visible impact
so that others can decide which kernel version(s) need the patch.
> --- a/fs/autofs4/symlink.c
> +++ b/fs/autofs4/symlink.c
> @@ -14,8 +14,9 @@
>
> static void *autofs4_follow_link(struct dentry *dentry, struct nameidata *nd)
> {
> + struct autofs_sb_info *sbi = autofs4_sbi(dentry->d_sb);
> struct autofs_info *ino = autofs4_dentry_ino(dentry);
> - if (ino)
> + if (ino && !autofs4_oz_mode(sbi))
> ino->last_used = jiffies;
> nd_set_link(nd, dentry->d_inode->i_private);
> return NULL;
What kernel is this against? 3.13-rc5 is quite different:
static void *autofs4_follow_link(struct dentry *dentry, struct nameidata *nd)
{
nd_set_link(nd, dentry->d_inode->i_private);
return NULL;
}
next prev parent reply other threads:[~2013-12-26 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 9:44 [PATCH] autofs - fix fix symlinks arent checked for expiry Ian Kent
2013-12-26 21:42 ` Andrew Morton [this message]
2013-12-27 1:09 ` Ian Kent
2013-12-27 1:19 ` Andrew Morton
2013-12-27 1:55 ` 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=20131226134253.5f4b2f02a00e11b8de49770e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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).