From: Nick Piggin <npiggin@suse.de>
To: David Howells <dhowells@redhat.com>
Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Add a dentry op to handle automounting rather than abusing follow_link
Date: Thu, 22 Jul 2010 14:15:54 +1000 [thread overview]
Message-ID: <20100722041554.GB3446@amd> (raw)
In-Reply-To: <27282.1279058150@redhat.com>
This hasn't had much comments yet.
On Tue, Jul 13, 2010 at 10:55:50PM +0100, David Howells wrote:
>
> Add a dentry op (d_automount) to handle automounting directories rather than
> abusing the follow_link() inode operation.
>
> I've only changed __follow_mount() to handle automount points, but it might be
> necessary to change follow_mount() too. The latter is only used from
> follow_dotdot(), but any automounts on ".." should be pinned whilst we're using
> a child of it.
>
> AFS is made to use this facility so that it can be tested. Other filesystems
> abusing the follow_mount() inode operation will also need to be modified.
How about having a .follow_mount op, and using that instead of
default follow_mount in case mounted is incremented?
Also I would prefer the patch to add this call keep basically the
same API as follow_mount, so if you are going to change that to
return an error and do the NOFOLLOW handling in there, then
could you do that first, as a more trivial patch?
Then your addition of the d_op should not touch outside
*follow_mount.
next prev parent reply other threads:[~2010-07-22 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 21:55 [RFC][PATCH] Add a dentry op to handle automounting rather than abusing follow_link David Howells
2010-07-13 22:48 ` [RFC][PATCH] xstat: Add an AT_NO_AUTOMOUNT flag to suppress terminal automount David Howells
2010-07-22 4:15 ` Nick Piggin [this message]
2010-07-22 12:36 ` [RFC][PATCH] Add a dentry op to handle automounting rather than abusing follow_link David Howells
2010-07-22 14:57 ` Nick Piggin
2010-07-22 15:33 ` David Howells
2010-07-22 16:04 ` 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=20100722041554.GB3446@amd \
--to=npiggin@suse.de \
--cc=dhowells@redhat.com \
--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).