linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Nick Piggin <npiggin@suse.de>, David Howells <dhowells@redhat.com>
Cc: 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>
Subject: Re: [PATCH 0/3] Fixes for vfs-scale and vfs-automount
Date: Wed, 19 Jan 2011 15:06:57 +0800	[thread overview]
Message-ID: <1295420817.3076.24.camel@perseus> (raw)
In-Reply-To: <20110118040449.23109.33071.stgit@localhost6.localdomain6>

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.

I have two tests, the first is the autofs connectathon test suite.
It consists of a wide range of automount map constructs, and contains
both success and failure cases and results in about 260 mounts. I
usually run the test 3 times, and wait for the mounts to expire between
runs.

The connectathon test worked fine and I didn't observe any unexpected
log messages over the three runs.

The second test I run has been adapted from one of the connectathon
tests. This test uses autofs submounts which are the most problematic of
the autofs map constructs. The modified test is meant to introduce a
fairly high level of contention by using a number of processes accessing
the mounts at the same time (currently configured as 10 processes). I
also attempt to introduce expire to mount contention by adjusting the
expire timeout. In addition the test runs twice, one the the default
nobrowse option and one for the browse option (no need to worry about
what that means). All in all the test seems to be fairly good at
exposing problems and 150 iterations of each configuration seems to get
most problems within three consecutive runs.

The first run of this test returned a pass although there were some
unexpected log messages. I'm not sure yet what is causing these. Of
interest was a bunch of reported lstat() failures against directories
that corresponded to failure cases and should not have existed at all.

The second run went through to completion but triggered the BUG() at
line 941 in shrink_dcache_for_umount_subtree() when shutting down autofs
after the first (nobrowse) part of the test run.

So, there is still a ref count problem somewhere, at least.

> 
> Nick, David, can you check my changes please, particularly the cases
> for the do_lookup() change.
> 
> ---
> 
> Ian Kent (3):
>       autofs4 - fix debug print in autofs4_lookup()
>       vfs - fix dentry ref count in do_lookup()
>       autofs4 - fix get_next_positive_dentry()
> 
> 
>  fs/autofs4/expire.c |    4 ++--
>  fs/autofs4/root.c   |    3 ++-
>  fs/namei.c          |    5 ++++-
>  3 files changed, 8 insertions(+), 4 deletions(-)
> 



  parent reply	other threads:[~2011-01-19  7:12 UTC|newest]

Thread overview: 24+ 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 ` Ian Kent [this message]
2011-02-15 14:25   ` [PATCH 0/3] Fixes for vfs-scale and vfs-automount Ian Kent
2011-02-23  7:22     ` Ian Kent
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
     [not found]           ` <20110224031439.GR22723-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
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
     [not found]                 ` <20110224035836.GS22723-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2011-02-24  6:34                   ` Ian Kent
2011-02-24  7:07                     ` Al Viro
     [not found]                       ` <20110224070724.GW22723-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
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 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=1295420817.3076.24.camel@perseus \
    --to=raven@themaw.net \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 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).