From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.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 tip/core/rcu 0/4] SRCU updates for v4.21/v5.0
Date: Sun, 11 Nov 2018 12:08:34 -0800 [thread overview]
Message-ID: <20181111200834.GA10983@linux.ibm.com> (raw)
Hello!
This series contains SRCU updates:
1. Fix kernel-doc missing notation, courtesy of Randy Dunlap.
2. Prevent __call_srcu() counter wrap with read-side critical section.
3. Lock srcu_data structure in srcu_gp_start(), fixing a an extremely
rare but also extremely embarrassing concurrency bug, courtesy
of Dennis Krein.
4. Use "ssp" instead of "sp" for srcu_struct pointer, in the hope
that this prevents confusion about which lock is held.
Thanx, Paul
------------------------------------------------------------------------
include/linux/srcu.h | 81 ++++---
include/linux/srcutiny.h | 24 +-
include/linux/srcutree.h | 8
kernel/rcu/srcutiny.c | 120 +++++------
kernel/rcu/srcutree.c | 493 +++++++++++++++++++++++------------------------
5 files changed, 367 insertions(+), 359 deletions(-)
next reply other threads:[~2018-11-11 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 20:08 Paul E. McKenney [this message]
2018-11-11 20:08 ` [PATCH tip/core/rcu 1/4] srcu: Fix kernel-doc missing notation Paul E. McKenney
2018-11-11 20:08 ` [PATCH tip/core/rcu 2/4] srcu: Prevent __call_srcu() counter wrap with read-side critical section Paul E. McKenney
2018-11-11 20:08 ` [PATCH tip/core/rcu 3/4] srcu: Lock srcu_data structure in srcu_gp_start() Paul E. McKenney
2018-11-11 20:08 ` [PATCH tip/core/rcu 4/4] srcu: Use "ssp" instead of "sp" for srcu_struct pointer 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=20181111200834.GA10983@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.