From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
kernel-team@fb.com, elver@google.com,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL kcsan] KCSAN commits for v5.10
Date: Fri, 9 Oct 2020 08:45:58 +0200 [thread overview]
Message-ID: <20201009064558.GC9972@gmail.com> (raw)
In-Reply-To: <20200914175133.GA14094@paulmck-ThinkPad-P72>
* Paul E. McKenney <paulmck@kernel.org> wrote:
> Hello, Ingo!
>
> This pull request contains KCSAN updates for v5.10. These have been
> subjected to LKML review, most recently here:
>
> https://lore.kernel.org/lkml/20200831181715.GA1530@paulmck-ThinkPad-P72
>
> All of these have also been subjected to the kbuild test robot and
> -next testing. The following changes since v5.9-rc1 are available in
> the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git kcsan
>
> for you to fetch changes up to cd290ec24633f51029dab0d25505fae7da0e1eda:
>
> kcsan: Use tracing-safe version of prandom (2020-08-30 21:50:13 -0700)
>
> ----------------------------------------------------------------
> Marco Elver (19):
> kcsan: Add support for atomic builtins
> objtool: Add atomic builtin TSAN instrumentation to uaccess whitelist
> kcsan: Add atomic builtin test case
> kcsan: Support compounded read-write instrumentation
> objtool, kcsan: Add __tsan_read_write to uaccess whitelist
> kcsan: Skew delay to be longer for certain access types
> kcsan: Add missing CONFIG_KCSAN_IGNORE_ATOMICS checks
> kcsan: Test support for compound instrumentation
> instrumented.h: Introduce read-write instrumentation hooks
> asm-generic/bitops: Use instrument_read_write() where appropriate
> locking/atomics: Use read-write instrumentation for atomic RMWs
> kcsan: Simplify debugfs counter to name mapping
> kcsan: Simplify constant string handling
> kcsan: Remove debugfs test command
> kcsan: Show message if enabled early
> kcsan: Use pr_fmt for consistency
> kcsan: Optimize debugfs stats counters
> bitops, kcsan: Partially revert instrumentation for non-atomic bitops
> kcsan: Use tracing-safe version of prandom
>
> include/asm-generic/atomic-instrumented.h | 330 ++++++++++-----------
> include/asm-generic/bitops/instrumented-atomic.h | 6 +-
> include/asm-generic/bitops/instrumented-lock.h | 2 +-
> .../asm-generic/bitops/instrumented-non-atomic.h | 30 +-
> include/linux/instrumented.h | 30 ++
> include/linux/kcsan-checks.h | 45 ++-
> kernel/kcsan/core.c | 210 +++++++++++--
> kernel/kcsan/debugfs.c | 130 ++------
> kernel/kcsan/kcsan-test.c | 128 +++++++-
> kernel/kcsan/kcsan.h | 12 +-
> kernel/kcsan/report.c | 10 +-
> kernel/kcsan/selftest.c | 8 +-
> lib/Kconfig.kcsan | 5 +
> scripts/Makefile.kcsan | 2 +-
> scripts/atomic/gen-atomic-instrumented.sh | 21 +-
> tools/objtool/check.c | 55 ++++
> 16 files changed, 677 insertions(+), 347 deletions(-)
Pulled into tip:locking/core, thanks a lot Paul!
Ingo
prev parent reply other threads:[~2020-10-09 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 17:51 Paul E. McKenney
2020-10-09 6:45 ` Ingo Molnar [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=20201009064558.GC9972@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome