projects / linux-2.6-microblaze.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 27ba76e) | patch
lockdep: Explicitly flag likely false-positive report
authorPaul E. McKenney <paulmck@kernel.org>
Mon, 5 Apr 2021 16:47:59 +0000 (09:47 -0700)
committerPaul E. McKenney <paulmck@kernel.org>
Mon, 10 May 2021 23:22:54 +0000 (16:22 -0700)
commit1feb2cc8db481b902272559ad7aae3c091762ad0
tree38ee8c9062b201de472d995ca4785989d0d61300tree | snapshot
parent27ba76e164fc83ffe6ceeb0415c427ad1191af6ccommit | diff
lockdep: Explicitly flag likely false-positive report

The reason that lockdep_rcu_suspicious() prints the value of debug_locks
is because a value of zero indicates a likely false positive.  This can
work, but is a bit obtuse.  This commit therefore explicitly calls out
the possibility of a false positive.

Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
kernel/locking/lockdep.c diff | blob | history
MicroBlaze GIT Repository