All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Nick Piggin <npiggin@suse.de>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] Fixes for vfs-scale and vfs-automount
Date: Wed, 23 Feb 2011 15:22:05 +0800	[thread overview]
Message-ID: <1298445725.20733.2.camel@perseus> (raw)
In-Reply-To: <1297779902.13007.86.camel@perseus>

On Tue, 2011-02-15 at 22:25 +0800, Ian Kent wrote:
> On Wed, 2011-01-19 at 15:06 +0800, Ian Kent wrote:
> > On Tue, 2011-01-18 at 12:05 +0800, Ian Kent wrote:
> > > I noticed a couple of problems which needed to be fixed before I can
> > > start testing.
> > 
> > Before I return to testing I thought I should let everyone know the
> > results so far, following the addition of the merged patches from this
> > thread.
> 
> Sorry for the large recipient list but I think there's a need.
> I've made very little progress on this but my most recent development
> deserves an update.
> 
> Most recent kernel used is 2.6.38-rc4.

Now at rc5, and still struggling with this but I have made some
progress.

Nick, what stops a dentry from going away during the rcu-walk?

Ian



  reply	other threads:[~2011-02-23  7:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  4:05 [PATCH 0/3] Fixes for vfs-scale and vfs-automount Ian Kent
2011-01-18  4:06 ` [PATCH 1/3] autofs4 - fix get_next_positive_dentry() Ian Kent
2011-01-18  4:06 ` [PATCH 2/3] vfs - fix dentry ref count in do_lookup() Ian Kent
2011-01-18  4:44   ` Al Viro
2011-01-18  4:06 ` [PATCH 3/3] autofs4 - fix debug print in autofs4_lookup() Ian Kent
2011-01-19  7:06 ` [PATCH 0/3] Fixes for vfs-scale and vfs-automount Ian Kent
2011-02-15 14:25   ` Ian Kent
2011-02-23  7:22     ` Ian Kent [this message]
2011-02-23 16:37       ` Linus Torvalds
2011-02-24  1:58     ` Al Viro
2011-02-24  3:03       ` Ian Kent
2011-02-24  3:14         ` Al Viro
2011-02-24  3:28           ` Ian Kent
2011-02-24  3:28             ` Ian Kent
2011-02-24  3:58             ` Al Viro
2011-02-24  5:47               ` Al Viro
2011-02-24  7:23                 ` Ian Kent
2011-02-24  6:34               ` Ian Kent
2011-02-24  6:34                 ` Ian Kent
2011-02-24  7:07                 ` Al Viro
2011-02-24 10:07                   ` Ian Kent
2011-02-24 10:07                     ` Ian Kent
2011-02-24 14:59                     ` Al Viro
2011-02-24 15:18                       ` Al Viro
2011-02-25  3:07                       ` Ian Kent
2011-02-24 19:10                     ` Al Viro
2011-02-24 19:10                       ` Al Viro
2011-02-24 10:21                   ` 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=1298445725.20733.2.camel@perseus \
    --to=raven@themaw.net \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.