Re: [PATCH] panic: lockdep: correct lock debugging state check

2016-04-26 Thread Shi, Yang
On 4/26/2016 5:39 AM, Peter Zijlstra wrote: On Mon, Apr 25, 2016 at 08:36:37PM -0700, Yang Shi wrote: When kernel oops happens, lock debugging is turned off by debug_locks_off() in oops_enter() via calling __debug_locks_off() which set debug_locks to 0 via xchg(). But, calling to __debug_locks_o

Re: [PATCH] panic: lockdep: correct lock debugging state check

2016-04-26 Thread Peter Zijlstra
On Mon, Apr 25, 2016 at 08:36:37PM -0700, Yang Shi wrote: > When kernel oops happens, lock debugging is turned off by debug_locks_off() > in oops_enter() via calling __debug_locks_off() which set debug_locks to 0 > via xchg(). But, calling to __debug_locks_off() to check lock debugging state > in a

[PATCH] panic: lockdep: correct lock debugging state check

2016-04-25 Thread Yang Shi
When kernel oops happens, lock debugging is turned off by debug_locks_off() in oops_enter() via calling __debug_locks_off() which set debug_locks to 0 via xchg(). But, calling to __debug_locks_off() to check lock debugging state in add_taint() called by oops_end() will always return false since xch