From: Linus Torvalds <torvalds@linux-foundation.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Ian Kent <raven@themaw.net>, Jeff Layton <jlayton@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
David Howells <dhowells@redhat.com>,
viro@zeniv.linux.org.uk, gregkh@suse.de,
linux-nfs@vger.kernel.org, leonardo.lists@gmail.com
Subject: Re: [PATCH] VFS: Suppress automount on [l]stat, [l]getxattr, etc.
Date: Mon, 26 Sep 2011 15:56:01 -0700 [thread overview]
Message-ID: <CA+55aFzi+0Z6HXJCxW=Uc1EZsp4qA00i+ihNcSX_v6bVTbU2BA@mail.gmail.com> (raw)
In-Reply-To: <1317076424.19951.32.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
On Mon, Sep 26, 2011 at 3:33 PM, Trond Myklebust
<Trond.Myklebust@netapp.com> wrote:
>
> Lookup permission checks would be replaced with open permission checks
> on the server.
>
> IOW: the operation could potentially fail due to a completely unrelated
> issue.
Quite frankly, that still sounds like a "I'm trying to make a problem
out of something that isn't actually a problem". And you still seem to
be unwilling to admit that LOOKUP_FOLLOW is a problem that has
actually been reported in real life, so you just cut out that part of
my question about how this would be a bigger issue.
But whatever. I can't really care, since it's a two-liner to add a new
flag, and then it falls down to "if you want to follow automounts, you
can set that flag instead".
Almost nobody is ever going to bother setting the flag anyway, since
LOOKUP_OPEN and LOOKUP_DIRECTORY are going to take care of all the
common cases.
So here. You can set LOOKUP_AUTOMOUNT to force an automount traversal. Ok?
Linus
[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 984 bytes --]
fs/namei.c | 2 +-
include/linux/namei.h | 1 +
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index f4788365ea22..09606fd83d57 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -739,7 +739,7 @@ static int follow_automount(struct path *path, unsigned flags,
* of the daemon to instantiate them before they can be used.
*/
if (!(flags & (LOOKUP_PARENT | LOOKUP_DIRECTORY |
- LOOKUP_OPEN | LOOKUP_CREATE)) &&
+ LOOKUP_OPEN | LOOKUP_CREATE | LOOKUP_AUTOMOUNT)) &&
path->dentry->d_inode)
return -EISDIR;
diff --git a/include/linux/namei.h b/include/linux/namei.h
index 76fe2c62ae71..e13dac7caab2 100644
--- a/include/linux/namei.h
+++ b/include/linux/namei.h
@@ -48,6 +48,7 @@ enum {LAST_NORM, LAST_ROOT, LAST_DOT, LAST_DOTDOT, LAST_BIND};
*/
#define LOOKUP_FOLLOW 0x0001
#define LOOKUP_DIRECTORY 0x0002
+#define LOOKUP_AUTOMOUNT 0x0004
#define LOOKUP_PARENT 0x0010
#define LOOKUP_REVAL 0x0020
next prev parent reply other threads:[~2011-09-26 22:56 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 13:45 [PATCH] VFS: Suppress automount on [l]stat, [l]getxattr, etc David Howells
2011-09-22 14:33 ` Miklos Szeredi
2011-09-22 16:04 ` Ian Kent
2011-09-22 16:30 ` Linus Torvalds
2011-09-22 16:45 ` Ian Kent
2011-09-22 17:35 ` Jeff Layton
2011-09-22 18:44 ` Jeff Layton
2011-09-22 19:20 ` Trond Myklebust
2011-09-22 22:57 ` Linus Torvalds
2011-09-23 0:56 ` Myklebust, Trond
2011-09-23 1:04 ` Linus Torvalds
2011-09-23 1:21 ` Trond Myklebust
2011-09-23 7:25 ` Miklos Szeredi
2011-09-23 10:57 ` Ian Kent
2011-09-23 3:15 ` Ian Kent
2011-09-23 10:33 ` David Howells
2011-09-23 14:34 ` Trond Myklebust
2011-09-23 14:46 ` Linus Torvalds
2011-09-23 15:01 ` Trond Myklebust
2011-09-23 15:15 ` Linus Torvalds
2011-09-23 15:41 ` Ian Kent
2011-09-23 16:19 ` Miklos Szeredi
2011-09-23 16:21 ` Linus Torvalds
2011-09-23 16:26 ` Linus Torvalds
[not found] ` <13920.1316796007@redhat.com! >
2011-09-23 16:54 ` David Howells
2011-09-23 17:18 ` Linus Torvalds
2011-09-23 16:40 ` David Howells
2011-09-23 16:47 ` Linus Torvalds
2011-09-23 15:18 ` David Howells
2011-09-23 16:10 ` Miklos Szeredi
2011-09-24 1:30 ` Ian Kent
2011-09-24 1:44 ` Linus Torvalds
2011-09-24 2:31 ` Ian Kent
2011-09-24 11:36 ` Jeff Layton
2011-09-24 15:56 ` Linus Torvalds
2011-09-26 5:11 ` Ian Kent
2011-09-26 20:48 ` Linus Torvalds
2011-09-26 21:13 ` Trond Myklebust
2011-09-26 21:24 ` Linus Torvalds
2011-09-26 21:31 ` Trond Myklebust
2011-09-26 22:24 ` Linus Torvalds
2011-09-26 22:33 ` Trond Myklebust
2011-09-26 22:56 ` Linus Torvalds [this message]
2011-09-26 23:09 ` Trond Myklebust
2011-09-26 23:26 ` Linus Torvalds
2011-09-27 0:59 ` Trond Myklebust
2011-09-27 1:18 ` Linus Torvalds
2011-09-27 4:24 ` Ian Kent
2011-09-27 3:57 ` Linus Torvalds
2011-09-27 4:16 ` Ian Kent
2011-09-27 4:35 ` Linus Torvalds
2011-09-27 4:51 ` Ian Kent
2011-09-27 14:32 ` Linus Torvalds
2011-09-27 15:11 ` Myklebust, Trond
2011-09-29 9:32 ` Ian Kent
2011-09-27 15:22 ` Linus Torvalds
2011-09-27 17:38 ` Greg KH
2011-09-27 17:51 ` Linus Torvalds
2011-09-27 18:00 ` Greg KH
2011-09-27 20:18 ` Miklos Szeredi
2011-09-27 22:38 ` Greg KH
2011-09-27 13:34 ` [PATCH 1/2] VFS: Fix the remaining automounter semantics regressions Trond Myklebust
2011-09-27 13:34 ` [PATCH 2/2] VFS: Document automounter semantics Trond Myklebust
2011-09-23 15:23 ` [PATCH] VFS: Suppress automount on [l]stat, [l]getxattr, etc David Howells
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='CA+55aFzi+0Z6HXJCxW=Uc1EZsp4qA00i+ihNcSX_v6bVTbU2BA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Trond.Myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=gregkh@suse.de \
--cc=jlayton@redhat.com \
--cc=leonardo.lists@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.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).