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 v2 2/5] scftorture: Reject empty workloads before starting helpers
Date: Sun, 8 Nov 2026 19:02:38 -0500 [thread overview]
Message-ID: <20261109000243.3936824-3-joelagnelf@nvidia.com> (raw)
In-Reply-To: <20261109000243.3936824-1-joelagnelf@nvidia.com>
A module loaded with nthreads=0 starts its statistics task, but cleanup
skips stopping that task. Unloading the module then leaves it executing
freed module text. Reject a zero thread count before starting helpers;
negative counts still select the online CPU count.
Also, when built as a module with reschedule-only, this leaves the
selector empty because resched_cpu() is unavailable to modules. It warns
while selecting an operation, invokes no callbacks, and can nevertheless
report SUCCESS. Reject an empty effective selector after filtering
unsupported operations.
Both failures were reproduced in a guest without the patches.
Signed-off-by: Joel Fernandes <joelagnelf@nvidia.com>
---
kernel/scftorture.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/kernel/scftorture.c b/kernel/scftorture.c
index 603b2dba1536..ff9a8271a464 100644
--- a/kernel/scftorture.c
+++ b/kernel/scftorture.c
@@ -588,6 +588,12 @@ static int __init scf_torture_init(void)
scftorture_print_module_parms("Start of test");
+ if (!nthreads) {
+ SCFTORTOUT_ERRSTRING("nthreads must be nonzero");
+ firsterr = -EINVAL;
+ goto unwind;
+ }
+
if (weight_resched <= 0 &&
weight_single <= 0 && weight_single_rpc <= 0 && weight_single_wait <= 0 &&
weight_many <= 0 && weight_many_wait <= 0 &&
@@ -636,6 +642,11 @@ static int __init scf_torture_init(void)
scf_sel_add(weight_many_wait1, SCF_PRIM_MANY, true);
scf_sel_add(weight_all1, SCF_PRIM_ALL, false);
scf_sel_add(weight_all_wait1, SCF_PRIM_ALL, true);
+ if (!scf_sel_array_len) {
+ SCFTORTOUT_ERRSTRING("no supported operations selected");
+ firsterr = -EINVAL;
+ goto unwind;
+ }
scf_sel_dump();
if (onoff_interval > 0) {
--
2.54.0
next prev parent reply other threads:[~2026-11-09 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 0:02 [PATCH v2 0/5] My torture test related fixes for v7.5 Joel Fernandes
2026-11-09 0:02 ` [PATCH v2 1/5] rcu-tasks: Track barrier callbacks in debugobjects Joel Fernandes
2026-11-09 0:02 ` Joel Fernandes [this message]
2026-11-09 0:02 ` [PATCH v2 3/5] scftorture: Protect the initial affinity check from hotplug Joel Fernandes
2026-11-09 0:02 ` [PATCH v2 4/5] kasan: Avoid an unrelated RCU warning in the callback test Joel Fernandes
2026-11-09 0:02 ` [PATCH v2 5/5] MAINTAINERS: Add scftorture to TORTURE-TEST MODULES Joel Fernandes
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=20261109000243.3936824-3-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®