From: Paul E. McKenney <paulmck@kernel.org>
Date: Wed, 4 Aug 2021 00:42:25 +0000 (-0700)
Subject: rcutorture: Suppressing read-exit testing is not an error
X-Git-Tag: v6.6.17~8957^2^4~6
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fda84866b1e68ab409074e7fcf1a7db800615445;p=platform%2Fkernel%2Flinux-rpi.git

rcutorture: Suppressing read-exit testing is not an error

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>
---

diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
index ab421526..59254fa 100644
--- a/kernel/rcu/rcutorture.c
+++ b/kernel/rcu/rcutorture.c
@@ -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;