diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2020-11-16 13:10:12 +0100 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2020-11-19 19:34:17 -0800 |
| commit | 6dbce04d8417ae706596366e16841d77c454ba52 (patch) | |
| tree | f4f34a632bbf504557cb50c2412d80225f8b0576 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | c583bcb8f5edd48c1798798e341f78afb9bf4f6f (diff) | |
rcu: Allow rcu_irq_enter_check_tick() from NMI
Eugenio managed to tickle #PF from NMI context which resulted in
hitting a WARN in RCU through irqentry_enter() ->
__rcu_irq_enter_check_tick().
However, this situation is perfectly sane and does not warrant an
WARN. The #PF will (necessarily) be atomic and not require messing
with the tick state, so early return is correct. This commit
therefore removes the WARN.
Fixes: aaf2bc50df1f ("rcu: Abstract out rcu_irq_enter_check_tick() from rcu_nmi_enter()")
Reported-by: "Eugenio Pérez" <eupm90@gmail.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions