From: Ian Kent <raven@themaw.net>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: akpm@osdl.org, autofs@linux.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] autofs4 needs to force fail return revalidate
Date: Wed, 21 Jun 2006 21:05:40 +0800 (WST) [thread overview]
Message-ID: <Pine.LNX.4.64.0606212103080.14481@raven.themaw.net> (raw)
In-Reply-To: <20060621122523.GX27946@ftp.linux.org.uk>
On Wed, 21 Jun 2006, Al Viro wrote:
> On Wed, Jun 21, 2006 at 02:18:15PM +0800, Ian Kent wrote:
> > While this problem has been present for a long time I've avoided resolving
> > it because it was not very visible. But now that autofs v5 has "mount and
> > expire on demand" of nested multiple mounts, such as is found when
> > mounting an export list from a server, solving the problem cannot be
> > avoided any longer.
> >
> > I've tried very hard to find a way to do this entirely within the
> > autofs4 module but have not been able to find a satisfactory way to
> > achieve it.
> >
> > So, I need to propose a change to the VFS.
>
> NAK in that form. Care to explain what should happen to mount tree
> when you do that to mountpoint?
>
The flag is never set if it a mount succeeds so there's never a tree under
it. But that's only my usage, so point taken.
Thinking about it that's not the only potential problem either.
Ian
next prev parent reply other threads:[~2006-06-21 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 6:18 [PATCH] autofs4 needs to force fail return revalidate Ian Kent
2006-06-21 6:39 ` Andrew Morton
2006-06-21 13:07 ` Ian Kent
2006-06-21 13:39 ` Ian Kent
2006-06-23 4:14 ` Ian Kent
2006-06-23 4:30 ` Andrew Morton
2006-06-23 6:43 ` Ian Kent
2006-07-10 10:24 ` Andrew Morton
2006-07-10 16:23 ` [autofs] " Ian Kent
2006-06-21 12:25 ` Al Viro
2006-06-21 13:05 ` Ian Kent [this message]
2006-06-21 13:37 ` [autofs] " Jeff Moyer
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=Pine.LNX.4.64.0606212103080.14481@raven.themaw.net \
--to=raven@themaw.net \
--cc=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.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).