rcutorture: Add test of holding scheduler locks across rcu_read_unlock()
authorPaul E. McKenney <paulmck@kernel.org>
Sun, 29 Mar 2020 01:53:25 +0000 (18:53 -0700)
committerPaul E. McKenney <paulmck@kernel.org>
Mon, 27 Apr 2020 18:03:50 +0000 (11:03 -0700)
commit52b1fc3f798d02a3a9d1cf7a84e98a795223410a
tree1b8f8f588009bf7d08e9d7eaef4512138cd3d84b
parent5f5fa7ea89dc82d34ed458f4d7a8634e8e9eefce
rcutorture: Add test of holding scheduler locks across rcu_read_unlock()

Now that it should be safe to hold scheduler locks across
rcu_read_unlock(), even in cases where the corresponding RCU read-side
critical section might have been preempted and boosted, the commit adds
a test of this capability to rcutorture.  This has been tested on current
mainline (which can deadlock in this situation), and lockdep duly reported
the expected deadlock.  On -rcu, lockdep is silent, thus far, anyway.

Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
kernel/rcu/rcutorture.c