diff options
author | Scott Wood <swood@redhat.com> | 2021-08-20 09:42:36 +0200 |
---|---|---|
committer | Paul E. McKenney <paulmck@kernel.org> | 2021-09-13 16:36:16 -0700 |
commit | 71921a9606ddbcc1d98c00eca7ae82c373d1fecd (patch) | |
tree | a31461792e9787cf93831605db29151ed7f0564d /arch/xtensa | |
parent | fd13fe16db0d82612b260640f4e26f6d9d1e11fd (diff) | |
download | linux-stable-71921a9606ddbcc1d98c00eca7ae82c373d1fecd.tar.gz linux-stable-71921a9606ddbcc1d98c00eca7ae82c373d1fecd.tar.bz2 linux-stable-71921a9606ddbcc1d98c00eca7ae82c373d1fecd.zip |
rcutorture: Avoid problematic critical section nesting on PREEMPT_RT
rcutorture is generating some nesting scenarios that are not compatible on PREEMPT_RT.
For example:
preempt_disable();
rcu_read_lock_bh();
preempt_enable();
rcu_read_unlock_bh();
The problem here is that on PREEMPT_RT the bottom halves have to be
disabled and enabled in preemptible context.
Reorder locking: start with BH locking and continue with then with
disabling preemption or interrupts. In the unlocking do it reverse by
first enabling interrupts and preemption and BH at the very end.
Ensure that on PREEMPT_RT BH locking remains unchanged if in
non-preemptible context.
Link: https://lkml.kernel.org/r/20190911165729.11178-6-swood@redhat.com
Link: https://lkml.kernel.org/r/20210819182035.GF4126399@paulmck-ThinkPad-P17-Gen-1
Signed-off-by: Scott Wood <swood@redhat.com>
[bigeasy: Drop ATOM_BH, make it only about changing BH in atomic
context. Allow enabling RCU in IRQ-off section. Reword commit message.]
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'arch/xtensa')
0 files changed, 0 insertions, 0 deletions