summaryrefslogtreecommitdiffstats
path: root/scripts/atomic
diff options
context:
space:
mode:
authorBart Van Assche2019-04-15 19:05:38 +0200
committerIngo Molnar2019-04-16 08:21:51 +0200
commit8b39adbee805c539a461dbf208b125b096152b1c (patch)
tree1b3a4f8d2b60690a7c750c13d7016aff52880f74 /scripts/atomic
parentMerge tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/ker... (diff)
downloadkernel-qcow2-linux-8b39adbee805c539a461dbf208b125b096152b1c.tar.gz
kernel-qcow2-linux-8b39adbee805c539a461dbf208b125b096152b1c.tar.xz
kernel-qcow2-linux-8b39adbee805c539a461dbf208b125b096152b1c.zip
locking/lockdep: Make lockdep_unregister_key() honor 'debug_locks' again
If lockdep_register_key() and lockdep_unregister_key() are called with debug_locks == false then the following warning is reported: WARNING: CPU: 2 PID: 15145 at kernel/locking/lockdep.c:4920 lockdep_unregister_key+0x1ad/0x240 That warning is reported because lockdep_unregister_key() ignores the value of 'debug_locks' and because the behavior of lockdep_register_key() depends on whether or not 'debug_locks' is set. Fix this inconsistency by making lockdep_unregister_key() take 'debug_locks' again into account. Signed-off-by: Bart Van Assche <bvanassche@acm.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Waiman Long <longman@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Cc: shenghui <shhuiw@foxmail.com> Fixes: 90c1cba2b3b3 ("locking/lockdep: Zap lock classes even with lock debugging disabled") Link: http://lkml.kernel.org/r/20190415170538.23491-1-bvanassche@acm.org Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'scripts/atomic')
0 files changed, 0 insertions, 0 deletions