From: Joel Fernandes <joelagnelf@nvidia.com>
To: linux-kernel@vger.kernel.org,
"Paul E . McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
Davidlohr Bueso <dave@stgolabs.net>
Cc: rcu@vger.kernel.org
Subject: [PATCH] torture: Forgive SMT-control failures in CPU-hotplug testing
Date: Thu, 12 Nov 2026 12:52:20 -0500 [thread overview]
Message-ID: <20261112175220.767903-1-joelagnelf@nvidia.com> (raw)
The onoff task ends rcutorture with "End of test: RCU_HOTPLUG" if any
CPU-hotplug attempt fails, other than -EBUSY during boot. Toggling
/sys/devices/system/cpu/smt/control while onoff runs causes two failures
that are not the test's fault. cpu_up() returns -EPERM for an SMT thread
that SMT control keeps offline, and device_online() and device_offline()
return 1 when the toggle already did the operation.
Repro: in a 16-vCPU guest (8 cores, 2 threads), run
"modprobe rcutorture onoff_interval=1 gp_exp=0" while looping
"echo off/on > smt/control" for 120 seconds. This ended in RCU_HOTPLUG,
with no reader errors. With this change it ends in SUCCESS.
Forgive these like boot-time -EBUSY, by not counting the attempt.
Signed-off-by: Joel Fernandes <joelagnelf@nvidia.com>
---
kernel/torture.c | 40 ++++++++++++++++++++++++++++------------
1 file changed, 28 insertions(+), 12 deletions(-)
diff --git a/kernel/torture.c b/kernel/torture.c
index 8c4e6b2fe8ba..b860c99e9ca7 100644
--- a/kernel/torture.c
+++ b/kernel/torture.c
@@ -194,6 +194,24 @@ int torture_num_online_cpus(void)
}
EXPORT_SYMBOL_GPL(torture_num_online_cpus);
+/*
+ * If the CPU-hotplug failure is not the torture test's fault, return a
+ * string saying why it is forgiven. Otherwise, return NULL.
+ */
+static const char *torture_onoff_forgive(int ret)
+{
+ // PCI probe frequently disables hotplug during boot.
+ if (!rcu_inkernel_boot_has_ended() && ret == -EBUSY)
+ return " (-EBUSY forgiven during boot)";
+ // Hotplug is forbidden, for example by SMT control.
+ if (ret == -EPERM)
+ return " (-EPERM forgiven, hotplug forbidden)";
+ // Something else, such as SMT control, already did the operation.
+ if (ret == 1)
+ return " (already in requested state, forgiven)";
+ return NULL;
+}
+
/*
* Attempt to take a CPU offline. Return false if the CPU is already
* offline or if it is not subject to CPU-hotplug operations. The
@@ -204,7 +222,7 @@ bool torture_offline(int cpu, long *n_offl_attempts, long *n_offl_successes,
{
unsigned long delta;
int ret;
- char *s;
+ const char *s;
unsigned long starttime;
if (!cpu_online(cpu) || !cpu_is_hotpluggable(cpu))
@@ -220,12 +238,11 @@ bool torture_offline(int cpu, long *n_offl_attempts, long *n_offl_successes,
(*n_offl_attempts)++;
ret = remove_cpu(cpu);
if (ret) {
- s = "";
- if (!rcu_inkernel_boot_has_ended() && ret == -EBUSY) {
- // PCI probe frequently disables hotplug during boot.
+ s = torture_onoff_forgive(ret);
+ if (s)
(*n_offl_attempts)--;
- s = " (-EBUSY forgiven during boot)";
- }
+ else
+ s = "";
if (verbose)
pr_alert("%s" TORTURE_FLAG
"torture_onoff task: offline %d failed%s: errno %d\n",
@@ -266,7 +283,7 @@ bool torture_online(int cpu, long *n_onl_attempts, long *n_onl_successes,
{
unsigned long delta;
int ret;
- char *s;
+ const char *s;
unsigned long starttime;
if (cpu_online(cpu) || !cpu_is_hotpluggable(cpu))
@@ -280,12 +297,11 @@ bool torture_online(int cpu, long *n_onl_attempts, long *n_onl_successes,
(*n_onl_attempts)++;
ret = add_cpu(cpu);
if (ret) {
- s = "";
- if (!rcu_inkernel_boot_has_ended() && ret == -EBUSY) {
- // PCI probe frequently disables hotplug during boot.
+ s = torture_onoff_forgive(ret);
+ if (s)
(*n_onl_attempts)--;
- s = " (-EBUSY forgiven during boot)";
- }
+ else
+ s = "";
if (verbose)
pr_alert("%s" TORTURE_FLAG
"torture_onoff task: online %d failed%s: errno %d\n",
--
2.54.0
reply other threads:[~2026-11-12 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261112175220.767903-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=boqun@kernel.org \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®