entry: Fix the incorrect ordering of lockdep and RCU check
authorThomas Gleixner <tglx@linutronix.de>
Wed, 4 Nov 2020 13:06:23 +0000 (14:06 +0100)
committerThomas Gleixner <tglx@linutronix.de>
Wed, 4 Nov 2020 17:06:14 +0000 (18:06 +0100)
commit9d820f68b2bdba5b2e7bf135123c3f57c5051d05
tree5bffbaa5d0616b2ba79f0d4194876730a22fdeca
parent3cea11cd5e3b00d91caf0b4730194039b45c5891
entry: Fix the incorrect ordering of lockdep and RCU check

When an exception/interrupt hits kernel space and the kernel is not
currently in the idle task then RCU must be watching.

irqentry_enter() validates this via rcu_irq_enter_check_tick(), which in
turn invokes lockdep when taking a lock. But at that point lockdep does not
yet know about the fact that interrupts have been disabled by the CPU,
which triggers a lockdep splat complaining about inconsistent state.

Invoking trace_hardirqs_off() before rcu_irq_enter_check_tick() defeats the
point of rcu_irq_enter_check_tick() because trace_hardirqs_off() uses RCU.

So use the same sequence as for the idle case and tell lockdep about the
irq state change first, invoke the RCU check and then do the lockdep and
tracer update.

Fixes: a5497bab5f72 ("entry: Provide generic interrupt entry/exit code")
Reported-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/87y2jhl19s.fsf@nanos.tec.linutronix.de
kernel/entry/common.c