All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	rcu@vger.kernel.org, Boqun Feng <boqun.feng@gmail.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Z qiang <qiang.zhang1211@gmail.com>
Subject: [GIT PULL] RCU fixes for v6.7-rc1
Date: Tue, 7 Nov 2023 11:56:26 +0100	[thread overview]
Message-ID: <ZUoX2lAwknn9JkEm@lothringen> (raw)

Hello Linus,

Please pull the latest RCU git tree from:

  git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git tags/rcu-fixes-v6.7

for you to fetch changes up to a80712b9cc7e57830260ec5e1feb9cdb59e1da2f:

  rcu/tasks-trace: Handle new PF_IDLE semantics (2023-11-01 22:12:03 +0100)

----------------------------------------------------------------
RCU fixes for v6.7

* Fix a lock inversion between scheduler and RCU introduced
  in v6.2-rc4. The scenario could trigger on any user of RCU_NOCB
  (mostly Android and also nohz_full).

* Fix PF_IDLE semantic changes introduced in v6.6-rc3 breaking some
  RCU-Tasks and RCU-Tasks-Trace expectations as to what exactly is
  an idle task. This resulted in potential spurious stalls and
  warnings.

----------------------------------------------------------------
Frederic Weisbecker (3):
      rcu: Introduce rcu_cpu_online()
      rcu/tasks: Handle new PF_IDLE semantics
      rcu/tasks-trace: Handle new PF_IDLE semantics

Peter Zijlstra (1):
      rcu: Break rcu_node_0 --> &rq->__lock order

 kernel/rcu/rcu.h   |  2 ++
 kernel/rcu/tasks.h | 32 +++++++++++++++++++++++++++++---
 kernel/rcu/tree.c  | 43 ++++++++++++++++++++++++++++++++-----------
 3 files changed, 63 insertions(+), 14 deletions(-)

             reply	other threads:[~2023-11-07 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 10:56 Frederic Weisbecker [this message]
2023-11-08 17:52 ` [GIT PULL] RCU fixes for v6.7-rc1 pr-tracker-bot

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=ZUoX2lAwknn9JkEm@lothringen \
    --to=frederic@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=neeraj.upadhyay@amd.com \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --cc=rcu@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 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.