torture: Eliminate torture_runnable and perf_runnable
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Wed, 22 Nov 2017 04:19:17 +0000 (20:19 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 11 Dec 2017 17:18:29 +0000 (09:18 -0800)
commita2f2577d96ad060b65eb909dd39b57d676754119
treef05ed19020bde2f8998d5a8e1ac873bfd7c5d8be
parent4ced3314fd3a73dabac4e8a41747883eff36c3e8
torture: Eliminate torture_runnable and perf_runnable

The purpose of torture_runnable is to allow rcutorture and locktorture
to be started and stopped via sysfs when they are built into the kernel
(as in not compiled as loadable modules).  However, the 0444 permissions
for both instances of torture_runnable prevent this use case from ever
being put into practice.  Given that there have been no complaints
about this deficiency, it is reasonable to conclude that no one actually
makes use of this sysfs capability.  The perf_runnable module parameter
for rcuperf is in the same situation.

This commit therefore removes both torture_runnable instances as well
as perf_runnable.

Reported-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Documentation/admin-guide/kernel-parameters.txt
Documentation/locking/locktorture.txt
include/linux/torture.h
kernel/locking/locktorture.c
kernel/rcu/rcuperf.c
kernel/rcu/rcutorture.c
kernel/torture.c
tools/testing/selftests/rcutorture/configs/lock/ver_functions.sh
tools/testing/selftests/rcutorture/configs/rcu/ver_functions.sh
tools/testing/selftests/rcutorture/configs/rcuperf/ver_functions.sh