On Wed, 12 Oct 2011, Hans Schillstrom wrote:
> Hello,
> I got this when I was testing a VLAN patch i.e. using Dave Millers net-next from today.
> When doing this on a single core i686 I got the warning every time,
> however ifenslave is not hanging it's just a warning
> Have not been testing this on a multicore jet.
>
> There is no warnings with a 3.0.4 kernel.
>
> Is this a known warning ?
>
> ~ # ifenslave bond0 eth1 eth2
>
> =============================================
> [ INFO: possible recursive locking detected ]
> 3.1.0-rc9+ #3
> ---------------------------------------------
> ifenslave/749 is trying to acquire lock:
> (&(&parent->list_lock)->rlock){-.-...}, at: [<c14234a0>] cache_flusharray+0x41/0xdb
>
> but task is already holding lock:
> (&(&parent->list_lock)->rlock){-.-...}, at: [<c14234a0>] cache_flusharray+0x41/0xdb
>
Hmm, the only candidate that I can see that may have caused this is
83835b3d9aec ("slab, lockdep: Annotate slab -> rcu -> debug_object ->
slab"). Could you try reverting that patch in your local tree and seeing
if it helps?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>