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>
Cc: rcu@vger.kernel.org
Subject: [PATCH v2 0/5] My torture test related fixes for v7.5
Date: Sun, 8 Nov 2026 19:02:36 -0500 [thread overview]
Message-ID: <20261109000243.3936824-1-joelagnelf@nvidia.com> (raw)
Some test related fixes for v7.5 from me. Sending a v2 as I had to add a
MAINTAINERS entry to fix git send-email.
Joel Fernandes (5):
rcu-tasks: Track barrier callbacks in debugobjects
scftorture: Reject empty workloads before starting helpers
scftorture: Protect the initial affinity check from hotplug
kasan: Avoid an unrelated RCU warning in the callback test
MAINTAINERS: Add scftorture to TORTURE-TEST MODULES
MAINTAINERS | 2 ++
kernel/rcu/tasks.h | 3 +++
kernel/scftorture.c | 30 +++++++++++++++++++++++-------
mm/kasan/kasan_test_c.c | 3 ++-
4 files changed, 30 insertions(+), 8 deletions(-)
--
2.54.0
next 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 Joel Fernandes [this message]
2026-11-09 0:02 ` [PATCH v2 1/5] rcu-tasks: Track barrier callbacks in debugobjects Joel Fernandes
2026-11-09 0:02 ` [PATCH v2 2/5] scftorture: Reject empty workloads before starting helpers Joel Fernandes
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-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=boqun@kernel.org \
--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®