From: Jeff Moyer <jmoyer@redhat.com>
To: raven@themaw.net
Cc: Andrew Morton <akpm@osdl.org>,
"Steinar H. Gunderson" <sgunderson@bigfoot.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Michael Blandford <michael@kmaclub.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] autofs4 - bad lookup fix
Date: Thu, 9 Jun 2005 14:26:06 -0400 [thread overview]
Message-ID: <17064.35262.790619.560855@segfault.boston.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0506041543090.8502@donald.themaw.net>
==> Regarding [PATCH] autofs4 - bad lookup fix; raven@themaw.net adds:
raven> For browsable autofs maps, a mount request that arrives at the same
raven> time an expire is happening can fail to perform the needed mount.
raven> This happens becuase the directory exists and so the revalidate
raven> succeeds when we need it to fail so that lookup is called on the
raven> same dentry to do the mount. Instead lookup is called on the next
raven> path component which should be whithin the mount, but the parent
raven> isn't mounted.
raven> The solution is to allow the revalidate to continue and perform the
raven> mount as no directory creation (at mount time) is needed for
raven> browsable mount entries.
I have a reproducer case for this, and the patch provided fixes it in my
environment.
-Jeff
prev parent reply other threads:[~2005-06-09 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 8:12 [PATCH] autofs4 - bad lookup fix raven
2005-06-09 18:26 ` 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=17064.35262.790619.560855@segfault.boston.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@kmaclub.com \
--cc=raven@themaw.net \
--cc=sgunderson@bigfoot.com \
/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).