linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Nick Piggin <npiggin@suse.de>
Subject: Re: 2.6.33.3-rt19 kernel BUG's
Date: Fri, 07 May 2010 17:39:13 -0700	[thread overview]
Message-ID: <1273279153.2776.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1273276725.17045.4.camel@localhost.localdomain>

On Fri, 2010-05-07 at 23:58 +0000, Fernando Lopez-Lezcano wrote:
> On Fri, 2010-05-07 at 16:43 -0700, john stultz wrote:
> > On Fri, 2010-05-07 at 12:41 +0200, Thomas Gleixner wrote:
> > > On Thu, 6 May 2010, Fernando Lopez-Lezcano wrote:
> > > 
> > > CC'ed John and Nick
> > > 
> > > > See below... just trying to boot (quad core desktop machine).
> > 
> > Ok. Got this to reproduce. Will hopefully have a fix for your soon.
> > 
> > Thanks for the bug report!
> 
> Thanks for looking at it! It had been a while since I had problems with
> rt so I could not understand why I could not login :-) 

Bah! I should have caught this faster. I kept thinking it had to be some
missed unlock of the sbi->fs_lock, but it ends up its just the
autofs4_lock.

Apparently the conversion from using the dcache_lock -> autofs4_lock
forgot that this function already grabs the autofs_lock for a small
moment, so we end up grabbing the lock, then a moment later grab it
again. Splat.

This patch should resolve it.

Signed-off-by: John Stultz <johnstul@us.ibm.com>

diff --git a/fs/autofs4/root.c b/fs/autofs4/root.c
index 5b26088..a7eaa32 100644
--- a/fs/autofs4/root.c
+++ b/fs/autofs4/root.c
@@ -438,12 +438,10 @@ static int autofs4_revalidate(struct dentry *dentry, struct nameidata *nd)
 	}
 
 	/* Check for a non-mountpoint directory with no contents */
-	spin_lock(&autofs4_lock);
 	if (S_ISDIR(dentry->d_inode->i_mode) &&
 	    !d_mountpoint(dentry) && list_empty(&dentry->d_subdirs)) {
 		DPRINTK("dentry=%p %.*s, emptydir",
 			 dentry, dentry->d_name.len, dentry->d_name.name);
-		spin_unlock(&autofs4_lock);
 
 		if (autofs4_need_mount(flags) || current->link_count) {
 			int status;






  reply	other threads:[~2010-05-08  0:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  1:53 2.6.33.3-rt19 kernel BUG's Fernando Lopez-Lezcano
2010-05-07 10:41 ` Thomas Gleixner
2010-05-07 23:43   ` john stultz
2010-05-07 23:58     ` Fernando Lopez-Lezcano
2010-05-08  0:39       ` john stultz [this message]
2010-05-10 17:11         ` Fernando Lopez-Lezcano
2010-05-10 20:02           ` john stultz
2010-05-10 23:23             ` Fernando Lopez-Lezcano

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=1273279153.2776.7.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=npiggin@suse.de \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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).