From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
kernel-team@fb.com, mingo@kernel.org, elver@google.com,
andreyknvl@google.com, glider@google.com, dvyukov@google.com
Subject: [GIT PULL] KCSAN changes for v5.17
Date: Mon, 10 Jan 2022 12:11:12 -0800 [thread overview]
Message-ID: <20220110201112.GA1013244@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Linus,
Please pull the latest KCSAN git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/kcsan.2022.01.09a
# HEAD: b473a3891c46393e9c4ccb4e3197d7fb259c7100: kcsan: Only test clear_bit_unlock_is_negative_byte if arch defines it
KCSAN changes for this cycle provide KCSAN fixes and also the ability to
take memory barriers into account for weakly-ordered systems. This last
can increase the probability of detecting certain types of data races.
----------------------------------------------------------------
Alexander Potapenko (1):
compiler_attributes.h: Add __disable_sanitizer_instrumentation
Marco Elver (28):
kcsan: Refactor reading of instrumented memory
kcsan: Remove redundant zero-initialization of globals
kcsan: Avoid checking scoped accesses from nested contexts
kcsan: Add core support for a subset of weak memory modeling
kcsan: Add core memory barrier instrumentation functions
kcsan, kbuild: Add option for barrier instrumentation only
kcsan: Call scoped accesses reordered in reports
kcsan: Show location access was reordered to
kcsan: Document modeling of weak memory
kcsan: test: Match reordered or normal accesses
kcsan: test: Add test cases for memory barrier instrumentation
kcsan: Ignore GCC 11+ warnings about TSan runtime support
kcsan: selftest: Add test case to check memory barrier instrumentation
locking/barriers, kcsan: Add instrumentation for barriers
locking/barriers, kcsan: Support generic instrumentation
locking/atomics, kcsan: Add instrumentation for barriers
asm-generic/bitops, kcsan: Add instrumentation for barriers
x86/barriers, kcsan: Use generic instrumentation for non-smp barriers
x86/qspinlock, kcsan: Instrument barrier of pv_queued_spin_unlock()
mm, kcsan: Enable barrier instrumentation
sched, kcsan: Enable memory barrier instrumentation
objtool, kcsan: Add memory barrier instrumentation to whitelist
objtool, kcsan: Remove memory barrier instrumentation from noinstr
kcsan: Support WEAK_MEMORY with Clang where no objtool support exists
kcsan: Make barrier tests compatible with lockdep
kcsan: Turn barrier instrumentation into macros
kcsan: Avoid nested contexts reading inconsistent reorder_access
kcsan: Only test clear_bit_unlock_is_negative_byte if arch defines it
Documentation/dev-tools/kcsan.rst | 76 +++-
arch/x86/include/asm/barrier.h | 10 +-
arch/x86/include/asm/qspinlock.h | 1 +
include/asm-generic/barrier.h | 54 ++-
include/asm-generic/bitops/instrumented-atomic.h | 3 +
include/asm-generic/bitops/instrumented-lock.h | 3 +
include/linux/atomic/atomic-instrumented.h | 135 ++++++-
include/linux/compiler_attributes.h | 18 +
include/linux/compiler_types.h | 13 +-
include/linux/kcsan-checks.h | 83 ++++-
include/linux/kcsan.h | 11 +-
include/linux/sched.h | 3 +
include/linux/spinlock.h | 2 +-
init/init_task.c | 5 -
kernel/kcsan/Makefile | 2 +
kernel/kcsan/core.c | 347 +++++++++++++++---
kernel/kcsan/kcsan_test.c | 426 +++++++++++++++++++++--
kernel/kcsan/report.c | 51 +--
kernel/kcsan/selftest.c | 143 ++++++++
kernel/sched/Makefile | 7 +-
lib/Kconfig.kcsan | 20 ++
mm/Makefile | 2 +
scripts/Makefile.kcsan | 15 +-
scripts/Makefile.lib | 5 +
scripts/atomic/gen-atomic-instrumented.sh | 41 ++-
tools/objtool/check.c | 41 ++-
tools/objtool/include/objtool/elf.h | 2 +-
27 files changed, 1347 insertions(+), 172 deletions(-)
next reply other threads:[~2022-01-10 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 20:11 Paul E. McKenney [this message]
2022-01-11 18:03 ` 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=20220110201112.GA1013244@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®