From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH v2 0/5] Miscellaneous RCU updates for v6.19
Date: Thu, 6 Nov 2025 00:06:10 +0100 [thread overview]
Message-ID: <aQvYYq3ym9mbHZb5@pavilion.home> (raw)
In-Reply-To: <cf8b57e0-1803-45e9-a217-9c9aeb64a2f9@paulmck-laptop>
Le Wed, Nov 05, 2025 at 12:19:51PM -0800, Paul E. McKenney a écrit :
> Hello!
>
> This series provides miscellaneous RCU updates:
>
> 1. Fix memory leak in param_set_cpumask(), courtesy of Wang Liang.
>
> 2. use WRITE_ONCE() for ->next and ->pprev of hlist_nulls, courtesy
> of Xuanqiang Luo.
>
> 3. Add kvm-series.sh to test commit/scenario combination.
>
> 4. Permit kvm-again.sh to re-use the build directory.
>
> 5. Remove redundant rcutorture_one_extend() from
> rcu_torture_one_read().
>
> Changes since v1:
>
> o Make kvm-again.sh able to reuse the rcutorture res directory
> in support of upcoming parallel execution of kvm-series.sh
> guest OSes. This is #3 above.
>
> o Remove a redundant call to rcutorture_one_extend(). This is
> #4 above.
>
> o Add the SPDX line to kvm-again.sh and remove a trailing space
> character from the comment header.
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> include/linux/rculist_nulls.h | 6
> kernel/locking/locktorture.c | 8 -
> kernel/rcu/rcutorture.c | 4
> tools/testing/selftests/rcutorture/bin/kvm-again.sh | 56 ++++++---
> tools/testing/selftests/rcutorture/bin/kvm-series.sh | 116 +++++++++++++++++++
> 5 files changed, 166 insertions(+), 24 deletions(-)
>
Applied to rcu/misc (and also applied the refscale patches for rcu/refscale).
Thanks!
--
Frederic Weisbecker
SUSE Labs
prev parent reply other threads:[~2025-11-05 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 20:19 [PATCH v2 0/5] Miscellaneous RCU updates for v6.19 Paul E. McKenney
2025-11-05 20:19 ` [PATCH v2 1/5] locktorture: Fix memory leak in param_set_cpumask() Paul E. McKenney
2025-11-05 20:19 ` [PATCH v2 2/5] rcu: use WRITE_ONCE() for ->next and ->pprev of hlist_nulls Paul E. McKenney
2025-11-05 20:19 ` [PATCH v2 3/5] torture: Add kvm-series.sh to test commit/scenario combination Paul E. McKenney
2025-11-05 20:19 ` [PATCH v2 4/5] rcutorture: Permit kvm-again.sh to re-use the build directory Paul E. McKenney
2025-11-05 20:20 ` [PATCH v2 5/5] rcutorture: Remove redundant rcutorture_one_extend() from rcu_torture_one_read() Paul E. McKenney
2025-11-05 23:06 ` Frederic Weisbecker [this message]
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=aQvYYq3ym9mbHZb5@pavilion.home \
--to=frederic@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).