All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Sage Weil <sage@newdream.net>
Cc: linux-fsdevel@vger.kernel.org, hch@infradead.org,
	akpm@linux-foundation.org, Al Viro <viro@zeniv.linux.org.uk>,
	Andreas Dilger <adilger@sun.com>,
	Yehuda Sadeh <yehuda@newdream.net>
Subject: Re: [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held
Date: Thu, 26 Mar 2009 17:00:10 +0900	[thread overview]
Message-ID: <49CB360A.1010601@themaw.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0903252022570.9205@cobra.newdream.net>

Sage Weil wrote:
> On Thu, 26 Mar 2009, Ian Kent wrote:
>>> Would it be possible to avoid the upcall in revalidate, and instead fail 
>>> and let the subsequent lookup path do it?  (I'm guessing the upcall 
>>> doesn't happen for _every_ revalidate?)
>> Yes, that's right, just every revalidate from processes that aren't the
>> automount process itself. The normal case is the mount succeeds and
>> further walks follow the mount from then on until it expires.
>>
>> It was more than three years ago when I tried to make everything go
>> through lookup so my memory is pretty unclear now. In the end I think
>> there was one case in real_lookup() where the lookup was skipped,
>> revalidate was called and failed but lookup wasn't then called again and
>> I got an incorrect failure.
> 
> That is _exactly_ the bug this patch is fixing.  :)  A (racing) process 
> ends up in real_lookup(), takes the mutex and finds the dentry has already 
> been added to the cache by someone else.  The mutex is dropped, revalidate 
> is called, and if it fails, real_lookup() returns ENOENT (!!) without ever 
> trying lookup.  The basic problem is that the fs revalidate might fail, 
> expecting lookup to get called, but real_lookup() returns ENOENT 
> instead... which is just wrong.
> 
>> AFAICR all other code paths that hold the
>> mutex over lookup and revalidate perform the revalidate first and then
>> the lookup if that fails, which avoids this case.
> 
> If you mean the paths autofs manages to avoid (unlinkat, rmdir, etc.), 
> yeah: the mutex is taken, then cached_lookup() (and revalidate), then 
> lookup if necessary.  Holding the mutex over revalidate avoids dealing 
> with various races.
> 
> So, it sounds like this fix would need to go in along with an autofs patch 
> that moves the upcall back into lookup exclusively, now that a revalidate 
> failure does the right thing (always calls lookup).  Hopefully that would 
> mean a net simplification on the autofs side as well?

Maybe ... doesn't look like it so far ... but it's to soon to tell.

autofs4 - always use lookup for mount

From: Ian Kent <raven@themaw.net>


---

 fs/autofs4/autofs_i.h |   15 ------
 fs/autofs4/root.c     |  117
++++++++++++++++++++++++++++++++++---------------
 2 files changed, 81 insertions(+), 51 deletions(-)

Ian


  reply	other threads:[~2009-03-26  8:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 20:16 [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held Sage Weil
2009-03-19 20:16 ` [PATCH 2/2] vfs: clean up real_lookup Sage Weil
2009-03-19 20:22   ` Christoph Hellwig
2009-03-19 20:35     ` Sage Weil
2009-03-19 20:23 ` [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held Christoph Hellwig
2009-03-24  4:14 ` Ian Kent
2009-03-24  4:18   ` Ian Kent
2009-03-25  4:29     ` Sage Weil
2009-03-25  6:08       ` Ian Kent
2009-03-25 16:11         ` Ian Kent
2009-03-25 19:11           ` Sage Weil
2009-03-26  2:09             ` Ian Kent
2009-03-26  3:53               ` Sage Weil
2009-03-26  8:00                 ` Ian Kent [this message]
2009-03-26 10:38                 ` Ian Kent
2009-03-29  8:53                   ` Ian Kent
2009-04-03  0:58                     ` Sage Weil
2009-04-03  2:00                       ` Ian Kent
2009-04-03  3:07                         ` Sage Weil
2009-06-22 17:15                         ` Sage Weil
2009-06-23  0:37                           ` Ian Kent
2009-06-23  2:40                             ` H. Peter Anvin
2009-06-25  7:21                               ` Ian Kent
2009-06-25 13:41                                 ` H. Peter Anvin
2009-06-25 13:58                                   ` Christoph Hellwig
2009-06-23  2:42                             ` H. Peter Anvin
2009-06-24  2:28                             ` Ian Kent
2009-06-24  5:45                               ` Sage Weil
2009-06-24  9:17                                 ` Ian Kent
2009-06-24 17:46                                   ` Sage Weil
2009-06-25  2:50                                     ` Ian Kent
2009-06-25  4:13                                     ` Ian Kent
2009-06-25  4:49                                       ` Sage Weil
2009-06-25  5:52                                         ` Ian Kent
2009-09-17  6:36                                           ` Ian Kent
2009-07-20  2:45                                 ` Ian Kent
2009-07-28 22:47                                   ` Sage Weil
2009-07-29  2:59                                     ` Ian Kent
2009-07-29 16:57                                       ` Sage Weil
2009-07-30  0:56                                         ` Ian Kent
2009-07-30 17:47                                           ` Sage Weil
2009-07-31  2:03                                             ` Ian Kent
2009-03-26  3:54               ` Ian Kent
2009-03-26  4:03                 ` Sage Weil
2009-03-26  5:07                 ` Ian Kent

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=49CB360A.1010601@themaw.net \
    --to=raven@themaw.net \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sage@newdream.net \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yehuda@newdream.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.