From: Jeff Moyer <jmoyer@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: akpm@osdl.org, autofs@linux.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [autofs] [PATCH] autofs4 needs to force fail return revalidate
Date: Wed, 21 Jun 2006 09:37:20 -0400 [thread overview]
Message-ID: <x49irmuhbov.fsf@segfault.boston.redhat.com> (raw)
In-Reply-To: <200606210618.k5L6IFDr008176@raven.themaw.net> (Ian Kent's message of "Wed, 21 Jun 2006 14:18:15 +0800")
==> Regarding [autofs] [PATCH] autofs4 needs to force fail return revalidate; Ian Kent <raven@themaw.net> adds:
raven> Hi Andrew,
raven> I didn't get any adverse (or other feedback) for this patch after
raven> posting an RFC to LKML so here it is.
raven> For a long time now I have had a problem with not being able to
raven> return a lookup failure on an existsing directory. In autofs this
raven> corresponds to a mount failure on a autofs managed mount entry that
raven> is browsable (and so the mount point directory exists).
raven> While this problem has been present for a long time I've avoided
raven> resolving it because it was not very visible. But now that autofs v5
raven> has "mount and expire on demand" of nested multiple mounts, such as
raven> is found when mounting an export list from a server, solving the
raven> problem cannot be avoided any longer.
raven> I've tried very hard to find a way to do this entirely within the
raven> autofs4 module but have not been able to find a satisfactory way to
raven> achieve it.
raven> So, I need to propose a change to the VFS.
raven> Signed-off-by: Ian Kent <raven@themaw.net>
Acked-by: Jeff Moyer <jmoyer@redhat.com>
-Jeff
prev parent reply other threads:[~2006-06-21 13:37 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
2006-06-21 13:37 ` Jeff Moyer [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=x49irmuhbov.fsf@segfault.boston.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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).