linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sage Weil <sage@newdream.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs pile, part 2
Date: Fri, 28 May 2010 20:47:53 +0100	[thread overview]
Message-ID: <20100528194753.GL31073@ZenIV.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1005281221090.27944@cobra.newdream.net>

On Fri, May 28, 2010 at 12:27:51PM -0700, Sage Weil wrote:
> Hi Al,
> 
> There are two patches
> 
>  1f24668c vfs: make real_lookup do dentry revalidation with i_mutex held
>  982ddae4 vfs: clean up do_lookup()
> 
> that were in your for-next a few weeks back but aren't anymore (they're 
> still in your autofs branch).  I just want to make sure those don't get 
> lost if they're not going to make it upstream this time around?  I think 
> they've been in vfs-2.6.git limbo for two release cycles now.

My apologies, I thought you'd been Cc'd on the discussions with Ian concerning
that stuff, but...

The bottom line: "autofs4: always use lookup for lookup" is needed for them
and it had to be reverted since it'd been FUBAR.

Details: we really, *really* can not do things in ->d_revalidate() and count
on ->lookup() to come and finish them.  Think for a minute and you'll see why -
between these two calls we allocate a dentry to pass to ->lookup().  What
happens if that allocation fails?

And without that patch your stuff breaks autofs4.  So it's waiting for the
->d_revalidate() interface redesign.  Hopefully in the coming cycle...

  reply	other threads:[~2010-05-28 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28 15:51 [git pull] vfs pile, part 2 Al Viro
2010-05-28 19:27 ` Sage Weil
2010-05-28 19:47   ` Al Viro [this message]
2010-05-29  9:07     ` Christoph Hellwig
2010-06-02 19:57 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2011-05-28 17:25 Al Viro

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=20100528194753.GL31073@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sage@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).