linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Sage Weil <sage@newdream.net>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	akpm@linux-foundation.org, Al Viro <viro@zeniv.linux.org.uk>,
	Andreas Dilger <adilger@sun.com>,
	Yehuda Sadeh <yehuda@newdream.net>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held
Date: Fri, 03 Apr 2009 10:00:53 +0800	[thread overview]
Message-ID: <49D56DD5.80707@themaw.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0904021751500.27228@cobra.newdream.net>

Sage Weil wrote:
>> Latest here works OK.
>>
>> I haven't finished checking yet but it looks like the patch below works 
>> OK. I started with a 2.6.29 build with your two patches but it was a 
>> little broken so I fell back to a Fedora 2.6.27 based kernel without the
>> two revalidate pacthes to debug it. So I still need to test the result 
>> against 2.6.29 again. I also don't have any real way to test for the three 
>> process race we discussed where the revalidate isn't followed by a 
>> ->lookup() but with both of your patches applied that shouldn't be a 
>> problem (as we discussed).
>>
>> I've not run checkpatch.pl against the patch either at this stage.
> 
> That's good news...

I'm still working on this too.
I have some pressing work so it may be a while before I'm totally happy
with the patch. Didn't you say you were expecting a 2.6.31 time frame
for this?

>  
>> There is a further issue and that is regarding the autofs module.
>>
>> I can't see updating autofs for this being practical (although I haven't 
>> actually looked yet). I suspect quite a bit of work would be needed. The 
>> fact is that autofs isn't used much any more and it really should be 
>> replaced with the autofs4 module at some point. But that's a fairly tricky 
>> exercise and will likely cause some user space breakage. It will require 
>> an updated module-init-tools to add "alais autofs4 autofs" for modprobe 
>> backward compatibility and will break for any explicit checks for the 
>> presence of the "autofs4" module.
> 
> Hmm.  Well, I assume autofs needs to work properly before this gets 
> changed, though, right?  Should I see what I can do with it?  I took a 
> quick look, and I don't think it will take too much to make it behave.  
> It looks like the main thing is to make the lookup call to try_fill_dentry 
> return any existing dentry in place of the one the vfs provides.

Yes, or be replaced by what is currently the autofs4 module. The autofs
v2 communication protocol surely can't be being used any more and the
autofs4 module supports versions 3, 4 and 5. In fact I received a mail
from HPA recently suggesting he supports doing this.

I had a quick look as well. I think you'll find it isn't quite as simple
as that. I'll have a closer look as soon as I get a chance.


Ian

  reply	other threads:[~2009-04-03  2:01 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
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 [this message]
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=49D56DD5.80707@themaw.net \
    --to=raven@themaw.net \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --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 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).