diff options
author | Sebastian Andrzej Siewior <bigeasy@linutronix.de> | 2020-11-03 20:09:37 +0100 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2020-11-15 20:59:26 +0100 |
commit | c725dafc95f1b37027840aaeaa8b7e4e9cd20516 (patch) | |
tree | 1abeecb6c63a7eb107a2b77e054f153c8ed822d0 /kernel/extable.c | |
parent | da88f9b3113620dcd30fc203236aa53d5430ee98 (diff) | |
download | linux-stable-c725dafc95f1b37027840aaeaa8b7e4e9cd20516.tar.gz linux-stable-c725dafc95f1b37027840aaeaa8b7e4e9cd20516.tar.bz2 linux-stable-c725dafc95f1b37027840aaeaa8b7e4e9cd20516.zip |
timers: Don't block on ->expiry_lock for TIMER_IRQSAFE timers
PREEMPT_RT does not spin and wait until a running timer completes its
callback but instead it blocks on a sleeping lock to prevent a livelock in
the case that the task waiting for the callback completion preempted the
callback.
This cannot be done for timers flagged with TIMER_IRQSAFE. These timers can
be canceled from an interrupt disabled context even on RT kernels.
The expiry callback of such timers is invoked with interrupts disabled so
there is no need to use the expiry lock mechanism because obviously the
callback cannot be preempted even on RT kernels.
Do not use the timer_base::expiry_lock mechanism when waiting for a running
callback to complete if the timer is flagged with TIMER_IRQSAFE.
Also add a lockdep assertion for RT kernels to validate that the expiry
lock mechanism is always invoked in preemptible context.
Reported-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20201103190937.hga67rqhvknki3tp@linutronix.de
Diffstat (limited to 'kernel/extable.c')
0 files changed, 0 insertions, 0 deletions