rcutorture: Suppressing read-exit testing is not an error
authorPaul E. McKenney <paulmck@kernel.org>
Wed, 4 Aug 2021 00:42:25 +0000 (17:42 -0700)
committerPaul E. McKenney <paulmck@kernel.org>
Mon, 13 Sep 2021 23:36:15 +0000 (16:36 -0700)
Currently, specifying the rcutorture.read_exit_burst=0 kernel boot
parameter will result in a -EINVAL exit code that will stop the rcutorture
test run before it has fully initialized.  This commit therefore uses a
zero exit code in that case, thus allowing rcutorture.read_exit_burst=0
to complete normally.

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
kernel/rcu/rcutorture.c

index ab42152..59254fa 100644 (file)
@@ -2741,7 +2741,7 @@ static int rcu_torture_read_exit(void *unused)
 static int rcu_torture_read_exit_init(void)
 {
        if (read_exit_burst <= 0)
-               return -EINVAL;
+               return 0;
        init_waitqueue_head(&read_exit_wq);
        read_exit_child_stop = false;
        read_exit_child_stopped = false;