From: "Paul E. McKenney" <paulmck@kernel.org>
To: mingo@kernel.org, tglx@linutronix.de
Cc: peterz@infradead.org, x86@kernel.org, elver@google.com,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [GIT RFC PULL rcu/urgent] Fix noinstr warnings for KCSAN
Date: Fri, 26 Jun 2020 07:31:17 -0700 [thread overview]
Message-ID: <20200626143117.GA1532@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200626041232.GA10544@paulmck-ThinkPad-P72>
On Thu, Jun 25, 2020 at 09:12:32PM -0700, Paul E. McKenney wrote:
> Hello!
>
> This pull request contains 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.
>
> This pull request is currently RFC pending ongoing -next testing.
And it has now cleared a round of -next testing! ;-)
Thanx, Paul
> This was not entirely free of drama, with Stephen needing to handle
> a merge conflict:
>
> https://lore.kernel.org/lkml/20200626131425.73ee4e27@canb.auug.org.au/
>
> However, the resolution looks straightforward to me. In addition,
> these two commits pass rcutorture testing and associated KCSAN testing.
>
> 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/paulmck/linux-rcu.git rcu/urgent
>
> for you to fetch changes up to b58e733fd774f3f4b49d9e7640d172a57e35200e:
>
> rcu: Fixup noinstr warnings (2020-06-25 08:24:32 -0700)
>
> ----------------------------------------------------------------
> 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(-)
prev parent reply other threads:[~2020-06-26 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 4:12 [GIT RFC PULL rcu/urgent] Fix noinstr warnings for KCSAN Paul E. McKenney
2020-06-26 14:31 ` Paul E. McKenney [this message]
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=20200626143117.GA1532@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).