Re: lockdep spew

[Daniel Walker <dwalker@mvista.com>]

On Tue, 2006-08-08 at 14:38 -0400, Dave Jones wrote:
> I don't think I've seen this one reported yet.
> This kernel was a 2.6.18rc3-gitSomething, but I don't think
> anything has changed recently that would explain this?
> 
> 		Dave
> 

I think something similar to this was reported by Thomas Gleixner on a
NUMA machine. The subject was "[BUG] Lockdep recursive locking in
kmem_cache_free" , there was a patch provided by Ravikiran G Thirumalai
that remove the warnings.

Daniel


> > #######
> > checking if image is initramfs...
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > ---------------------------------------------
> > swapper/1 is trying to acquire lock:
> >  (&nc->lock){....}, at: [<ffffffff8020782c>] kmem_cache_free+0x1a1/0x26c
> > 
> > but task is already holding lock:
> >  (&nc->lock){....}, at: [<ffffffff8020b47e>] kfree+0x1b3/0x27e
> > 
> > other info that might help us debug this:
> > 2 locks held by swapper/1:
> >  #0:  (&nc->lock){....}, at: [<ffffffff8020b47e>] kfree+0x1b3/0x27e
> >  #1:  (&parent->list_lock){....}, at: [<ffffffff802dae22>]
> > __drain_alien_cache+0x37/0
> > x77


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/