[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231103072639.11426-1-qiang.zhang1211@gmail.com>
Date: Fri, 3 Nov 2023 15:26:39 +0800
From: Zqiang <qiang.zhang1211@...il.com>
To: paulmck@...nel.org, frederic@...nel.org, joel@...lfernandes.org
Cc: qiang.zhang1211@...il.com, rcu@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] rcutorture: Add fqs_holdoff check before the fqs_task is created
For rcutorture tests that support fqs operations and set fqs_duration
greater than zero, the fqs_task kthread will be created. but if the
fqs_holdoff is not set, the default value is zero, this cause fqs_task
enter a long-term busy loop and won't voluntarily give up the CPU until
stopped by kthread_stop(). this commit therefore add for fqs_holdoff check
before the fqs_task is created, make sure the fqs_task is created when
the fqs_holdoff is also greater than zero.
Signed-off-by: Zqiang <qiang.zhang1211@...il.com>
---
kernel/rcu/rcutorture.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
index 83999e57b3ea..9f0e6c1cad44 100644
--- a/kernel/rcu/rcutorture.c
+++ b/kernel/rcu/rcutorture.c
@@ -3886,7 +3886,9 @@ rcu_torture_init(void)
}
if (fqs_duration < 0)
fqs_duration = 0;
- if (fqs_duration) {
+ if (fqs_holdoff < 0)
+ fqs_holdoff = 0;
+ if (fqs_duration && fqs_holdoff) {
/* Create the fqs thread */
firsterr = torture_create_kthread(rcu_torture_fqs, NULL,
fqs_task);
--
2.17.1
Powered by blists - more mailing lists