From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] rcu/urgent for 5.8-rc3
Date: Sun, 28 Jun 2020 16:38:35 +0200 [thread overview]
Message-ID: <20200628143835.GC18884@zn.tnic> (raw)
Hi Linus,
please pull two urgent RCU, KCSAN-related fixes.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/rcu_urgent_for_5.8_rc3
for you to fetch changes up to b58e733fd774f3f4b49d9e7640d172a57e35200e:
rcu: Fixup noinstr warnings (2020-06-25 08:24:32 -0700)
----------------------------------------------------------------
Paul E. McKenney says:
A single commit that uses "arch_" atomic operations to avoid the
instrumentation that comes with the non-"arch_" versions. In preparation
for that commit, it also has another commit that makes these "arch_"
atomic operations available to generic code.
Without these commits, KCSAN uses can see pointless errors.
Both from Peter Zijlstra.
----------------------------------------------------------------
Peter Zijlstra (2):
locking/atomics: Provide the arch_atomic_ interface to generic code
rcu: Fixup noinstr warnings
include/linux/atomic-fallback.h | 236 +++++++++++++++++++++++++++++++++-
include/linux/compiler.h | 2 +-
kernel/rcu/tree.c | 32 ++++-
scripts/atomic/gen-atomic-fallback.sh | 31 +++++
4 files changed, 292 insertions(+), 9 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-06-28 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 14:38 Borislav Petkov [this message]
2020-06-28 18:45 ` [GIT PULL] rcu/urgent for 5.8-rc3 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=20200628143835.GC18884@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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