rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
	mingo@kernel.org, jiangshanlai@gmail.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org
Subject: [PATCH rcu 0/7] In-kernel torture-test updates for v5.16
Date: Wed, 15 Sep 2021 17:13:29 -0700	[thread overview]
Message-ID: <20210916001329.GA3909068@paulmck-ThinkPad-P17-Gen-1> (raw)

Hello!

This series contains in-kernel torture-test updates (excluding scftorture,
which has its own branch this time).

1.	Suppressing read-exit testing is not an error.

2.	Warn on individual rcu_torture_init() error conditions.

3.	Warn on individual lock_torture_init() error conditions.

4.	Warn on individual ref_scale_init() error conditions.

5.	Warn on individual rcu_scale_init() error conditions.

6.	Don't cpuhp_remove_state() if cpuhp_setup_state() failed.

7.	Avoid problematic critical section nesting on PREEMPT_RT,
	courtesy of Scott Wood.

						Thanx, Paul

------------------------------------------------------------------------

 b/include/linux/torture.h      |    8 ++++
 b/kernel/locking/locktorture.c |   14 +++----
 b/kernel/rcu/rcuscale.c        |   10 ++---
 b/kernel/rcu/rcutorture.c      |    2 -
 b/kernel/rcu/refscale.c        |    6 +--
 kernel/rcu/rcutorture.c        |   82 ++++++++++++++++++++++++++---------------
 6 files changed, 77 insertions(+), 45 deletions(-)

             reply	other threads:[~2021-09-16  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  0:13 Paul E. McKenney [this message]
2021-09-16  0:13 ` [PATCH rcu 1/7] rcutorture: Suppressing read-exit testing is not an error Paul E. McKenney
2021-09-16  0:13 ` [PATCH rcu 2/7] rcutorture: Warn on individual rcu_torture_init() error conditions Paul E. McKenney
2021-09-16  0:13 ` [PATCH rcu 3/7] locktorture: Warn on individual lock_torture_init() " Paul E. McKenney
2021-09-16  0:13 ` [PATCH rcu 4/7] refscale: Warn on individual ref_scale_init() " Paul E. McKenney
2021-09-16  0:13 ` [PATCH rcu 5/7] rcuscale: Warn on individual rcu_scale_init() " Paul E. McKenney
2021-09-16  0:13 ` [PATCH rcu 6/7] rcutorture: Don't cpuhp_remove_state() if cpuhp_setup_state() failed Paul E. McKenney
2021-09-16  0:13 ` [PATCH rcu 7/7] rcutorture: Avoid problematic critical section nesting on PREEMPT_RT Paul E. McKenney

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=20210916001329.GA3909068@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --subject='Re: [PATCH rcu 0/7] In-kernel torture-test updates for v5.16' \
    /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

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).