summaryrefslogtreecommitdiffstats
path: root/kernel/rcu
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2021-04-05 09:47:59 -0700
committerPaul E. McKenney <paulmck@kernel.org>2021-05-10 16:22:54 -0700
commit1feb2cc8db481b902272559ad7aae3c091762ad0 (patch)
tree38ee8c9062b201de472d995ca4785989d0d61300 /kernel/rcu
parent27ba76e164fc83ffe6ceeb0415c427ad1191af6c (diff)
downloadlinux-1feb2cc8db481b902272559ad7aae3c091762ad0.tar.gz
linux-1feb2cc8db481b902272559ad7aae3c091762ad0.tar.bz2
linux-1feb2cc8db481b902272559ad7aae3c091762ad0.zip
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>
Diffstat (limited to 'kernel/rcu')
0 files changed, 0 insertions, 0 deletions