From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756441Ab0EJUCu (ORCPT ); Mon, 10 May 2010 16:02:50 -0400 Received: from e9.ny.us.ibm.com ([32.97.182.139]:46391 "EHLO e9.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756312Ab0EJUCs (ORCPT ); Mon, 10 May 2010 16:02:48 -0400 Subject: Re: 2.6.33.3-rt19 kernel BUG's From: john stultz To: Fernando Lopez-Lezcano Cc: Thomas Gleixner , LKML , rt-users , Steven Rostedt , Nick Piggin In-Reply-To: <1273511465.21774.11.camel@localhost.localdomain> References: <1273197218.6768.10.camel@localhost.localdomain> <1273275821.2776.3.camel@localhost.localdomain> <1273276725.17045.4.camel@localhost.localdomain> <1273279153.2776.7.camel@localhost.localdomain> <1273511465.21774.11.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Mon, 10 May 2010 13:02:41 -0700 Message-ID: <1273521761.3843.33.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2010-05-10 at 10:11 -0700, Fernando Lopez-Lezcano wrote: > On Fri, 2010-05-07 at 17:39 -0700, john stultz wrote: > > 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. > > I'm still having problems when trying to use autofs, even with your > previous patch: Oof.. More of the same autofs4_lock misuse. I skimmed over the rest of its use, and it seems ok, so hopefully we won't hit any more problems caused by it. Here's both autofs4_lock changes together. Signed-off-by: John Stultz d_lock); if (ino->flags & AUTOFS_INF_PENDING || (!d_mountpoint(dentry) && list_empty(&dentry->d_subdirs))) { @@ -438,12 +437,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;