diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2020-10-02 11:04:21 +0200 |
|---|---|---|
| committer | Ingo Molnar <mingo@kernel.org> | 2020-10-09 08:53:30 +0200 |
| commit | 4d004099a668c41522242aa146a38cc4eb59cb1e (patch) | |
| tree | 9a8023c8fdbe431b9edbbcb2621dbf5c6bb4367b /net | |
| parent | 2bb8945bcc1a768f2bc402a16c9610bba8d5187d (diff) | |
| download | linux-4d004099a668c41522242aa146a38cc4eb59cb1e.tar.bz2 | |
lockdep: Fix lockdep recursion
Steve reported that lockdep_assert*irq*(), when nested inside lockdep
itself, will trigger a false-positive.
One example is the stack-trace code, as called from inside lockdep,
triggering tracing, which in turn calls RCU, which then uses
lockdep_assert_irqs_disabled().
Fixes: a21ee6055c30 ("lockdep: Change hardirq{s_enabled,_context} to per-cpu variables")
Reported-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions