diff options
| author | Paul E. McKenney <paulmck@kernel.org> | 2021-04-05 19:47:59 +0300 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2021-05-11 02:22:54 +0300 |
| commit | 1feb2cc8db481b902272559ad7aae3c091762ad0 (patch) | |
| tree | 38ee8c9062b201de472d995ca4785989d0d61300 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 27ba76e164fc83ffe6ceeb0415c427ad1191af6c (diff) | |
| download | linux-1feb2cc8db481b902272559ad7aae3c091762ad0.tar.xz | |
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 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions