Re: 2.6.33.3-rt19 kernel BUG's

[Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>]

On Mon, 2010-05-10 at 13:02 -0700, john stultz wrote:
> 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.

Thanks for the patch. It looks like it is working fine now, at least I
was able to login with an nfs/autofs mounted home dir...

-- Fernando