From: Ian Kent <raven@themaw.net>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
autofs mailing list <autofs@linux.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] autofs4 - use lookup access intent to support recursive bind mounts
Date: Mon, 28 Apr 2008 15:53:40 +0800 [thread overview]
Message-ID: <1209369220.3243.18.camel@raven.themaw.net> (raw)
In-Reply-To: <1209367536.3243.16.camel@raven.themaw.net>
On Mon, 2008-04-28 at 15:25 +0800, Ian Kent wrote:
> > ->lookup() and friends are going to stop getting struct nameidata *.
> > ->follow_link() obviously will keep it; ->d_revalidate() should
> > lose the sucker, but we might have to split it in two methods (which
> > is probably what'll be needed in your case).
>
> Right.
Would it be sensible to use dentry->d_flags for this purpose?
Ian
prev parent reply other threads:[~2008-04-28 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 6:14 [PATCH] autofs4 - use lookup access intent to support recursive bind mounts Ian Kent
2008-04-28 6:22 ` Al Viro
2008-04-28 6:38 ` Ian Kent
2008-04-28 7:05 ` Al Viro
2008-04-28 7:25 ` Ian Kent
2008-04-28 7:53 ` Ian Kent [this message]
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=1209369220.3243.18.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=autofs@linux.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).