From: Ian Kent <raven@themaw.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
miklos@szeredi.hu, viro@zeniv.linux.org.uk, jlayton@redhat.com,
gregkh@suse.de, linux-nfs@vger.kernel.org,
leonardo.lists@gmail.com
Subject: Re: [PATCH] NFS4: Revert commit to make the automount code ignore LOOKUP_FOLLOW
Date: Thu, 22 Sep 2011 23:54:19 +0800 [thread overview]
Message-ID: <1316706859.3346.37.camel@perseus.themaw.net> (raw)
In-Reply-To: <6490.1316704925@redhat.com>
On Thu, 2011-09-22 at 16:22 +0100, David Howells wrote:
>
> I would also say that we do not want lstat(), l*xattr() and co. to cause
> automounting - but maybe they should. Perhaps if you don't want to cause
> automounting, you should explicitly pass AT_NO_AUTOMOUNT, and all path-taking
> VFS calls should have variants that accept this flag.
I still think we had it right the first time.
After all we have always said automounts are directories that have
symlink semantics, which to my way of thinking is what we now have (or
had). Not only that, it provides a natural way of ensuring a mount
occurs or does not occur by using the well known no follow calls.
The "natural" part of this is automounts can be followed conceptually in
the same way that symlinks can be followed.
I
next prev parent reply other threads:[~2011-09-22 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 12:46 [PATCH] NFS4: Revert commit to make the automount code ignore LOOKUP_FOLLOW David Howells
2011-09-22 12:50 ` David Howells
2011-09-22 12:58 ` Miklos Szeredi
2011-09-22 13:41 ` David Howells
2011-09-22 14:23 ` Miklos Szeredi
2011-09-22 14:33 ` Linus Torvalds
2011-09-22 15:22 ` David Howells
2011-09-22 15:32 ` Miklos Szeredi
2011-09-22 15:33 ` Jeff Layton
2011-09-22 15:54 ` Ian Kent [this message]
2011-09-22 15:26 ` Jeff Layton
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=1316706859.3346.37.camel@perseus.themaw.net \
--to=raven@themaw.net \
--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=torvalds@linux-foundation.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