Re: WARNING: at kernel/lockdep.c:690 __lock_acquire+0x168/0x164b()

[David Rientjes]

On Thu, 20 Oct 2011, Sergey Senozhatsky wrote:

> > > FWIW,
> > > 
> > > the box has been running here with f59de8992aa6 reverted for a couple of
> > > days now and no sign of the warning. I'll keep watching it but it looks
> > > ok so far, so David, you could've nailed it.
> > > 
> > 
> > Hello,
> > Well, the same with me. My laptop has been running with reverted f59de8992aa6 without any
> > problems so far. Yet, I'm not sure I understand how memset() and loop could
> > produce different results.
> > 
> 
> Oh, well, nevermind I think I get it. 
> 
> Reverting opens https://bugzilla.kernel.org/show_bug.cgi?id=35532 again.  
> 

I don't know what that is since bugzilla.kernel.org is down :)  The 
problem is that the memset(), in addition to all the other fields in 
lockdep_map, clears the "name" field, which is what the scheduler uses 
via lock_set_sublcass() to prevent this lockdep warning.  My initial 
speculation seems to be confirmed since either you or Borislav have been 
able to reproduce the warning since removing the memset().

Tejun, would you like to revert f59de8992aa6 ("lockdep: Clear whole 
lockdep_map on initialization") since it fixes this lockdep warning?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/