Re: [Patch net] bridge: resolve a false alarm of lockdep

2017-03-16 Thread David Miller
From: Nikolay Aleksandrov Date: Thu, 16 Mar 2017 19:36:07 +0200 > On 16/03/17 19:32, Cong Wang wrote: >> Andrei reported a false alarm of lockdep at net/bridge/br_fdb.c:109, >> this is because in Andrei's case, a spin_bug() was already triggered >> before this, therefore the debug_locks is turned

Re: [Patch net] bridge: resolve a false alarm of lockdep

2017-03-16 Thread Nikolay Aleksandrov
On 16/03/17 19:32, Cong Wang wrote: > Andrei reported a false alarm of lockdep at net/bridge/br_fdb.c:109, > this is because in Andrei's case, a spin_bug() was already triggered > before this, therefore the debug_locks is turned off, lockdep_is_held() > is no longer accurate after that. We should u

[Patch net] bridge: resolve a false alarm of lockdep

2017-03-16 Thread Cong Wang
Andrei reported a false alarm of lockdep at net/bridge/br_fdb.c:109, this is because in Andrei's case, a spin_bug() was already triggered before this, therefore the debug_locks is turned off, lockdep_is_held() is no longer accurate after that. We should use lockdep_assert_held_once() instead of loc