From: "Paul E. McKenney" <paulmck@linux.vnet.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/5] Pre-gp_seq miscellaneous fixes for v4.19
Date: Mon, 25 Jun 2018 16:04:10 -0700 [thread overview]
Message-ID: <20180625230410.GA13250@linux.vnet.ibm.com> (raw)
Hello!
The following miscellaneous fixes come before the infamous ->gp_seq
conversion:
1. Add debugging info to the assertion detecting tasks queued on
the ->blkd_tasks list at unexpected times.
2. Use the proper lockdep annotation in dump_blkd_tasks(), courtesy
of Boqun Feng.
3. Exclude near-simultaneous RCU CPU stall warnings, thus reducing
the probability of interleaved (and thus inscrutable) warnings.
4. Add diagnostics for failure to respond to a request for a new
grace period.
5. Make rcu_gp_cleanup() write only once to ->gp_flags.
Thanx, Paul
------------------------------------------------------------------------
tree.c | 97 ++++++++++++++++++++++++++++++++++++++++++++++------------
tree.h | 4 ++
tree_plugin.h | 40 ++++++++++++++++++++++-
3 files changed, 119 insertions(+), 22 deletions(-)
next reply other threads:[~2018-06-25 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 23:04 Paul E. McKenney [this message]
2018-06-25 23:04 ` [PATCH tip/core/rcu 1/5] rcu: Add debugging info to assertion Paul E. McKenney
2018-06-25 23:04 ` [PATCH tip/core/rcu 2/5] rcu: Use the proper lockdep annotation in dump_blkd_tasks() Paul E. McKenney
2018-06-25 23:04 ` [PATCH tip/core/rcu 3/5] rcu: Exclude near-simultaneous RCU CPU stall warnings Paul E. McKenney
2018-06-25 23:04 ` [PATCH tip/core/rcu 4/5] rcu: Diagnostics for grace-period hangs Paul E. McKenney
2018-07-04 6:46 ` [lkp-robot] [rcu] 9165c9007c: WARNING:possible_recursive_locking_detected kernel test robot
2018-06-25 23:04 ` [PATCH tip/core/rcu 5/5] rcu: Make rcu_gp_cleanup() write only once to ->gp_flags 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=20180625230410.GA13250@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.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.