From: "Paul E. McKenney" <paulmck@kernel.org>
To: mingo@kernel.org, tglx@linutronix.de
Cc: kasan-dev@googlegroups.com, elver@google.com,
linux-kernel@vger.kernel.org, hqjagain@gmail.com,
weiyongjun1@huawei.com
Subject: [GIT PULL kcsan] KCSAN commits for v5.8
Date: Thu, 7 May 2020 16:12:27 -0700 [thread overview]
Message-ID: <20200507231227.GA12010@paulmck-ThinkPad-P72> (raw)
Hello!
This pull request contains KCSAN updates for v5.8. These have been
subject to LKML review:
https://lore.kernel.org/lkml/20200415183343.GA12265@paulmck-ThinkPad-P72
https://lore.kernel.org/lkml/20200417025837.49780-1-weiyongjun1@huawei.com
https://lore.kernel.org/lkml/20200401101714.44781-1-elver@google.com
https://lore.kernel.org/lkml/20200424154730.190041-1-elver@google.com
https://lore.kernel.org/lkml/20200424154730.190041-2-elver@google.com
All of these have also been subjected to the kbuild test robot and
-next testing. The following changes since commit f5d2313bd3c5:
kcsan, trace: Make KCSAN compatible with tracing (2020-03-21 09:44:41 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git kcsan-for-tip
for you to fetch changes up to 50a19ad4b1ec531eb550183cb5d4ab9f25a56bf8:
objtool, kcsan: Add kcsan_disable_current() and kcsan_enable_current_nowarn() (2020-05-06 13:47:06 -0700)
----------------------------------------------------------------
Ingo Molnar (1):
Improve KCSAN documentation a bit
Marco Elver (17):
kcsan: Add option to allow watcher interruptions
kcsan: Add option for verbose reporting
kcsan: Add current->state to implicitly atomic accesses
kcsan: Update Documentation/dev-tools/kcsan.rst
kcsan: Update API documentation in kcsan-checks.h
kcsan: Introduce report access_info and other_info
kcsan: Avoid blocking producers in prepare_report()
kcsan: Add support for scoped accesses
objtool, kcsan: Add explicit check functions to uaccess whitelist
kcsan: Introduce scoped ASSERT_EXCLUSIVE macros
kcsan: Move kcsan_{disable,enable}_current() to kcsan-checks.h
kcsan: Change data_race() to no longer require marking racing accesses
kcsan: Fix function matching in report
kcsan: Make reporting aware of KCSAN tests
checkpatch: Warn about data_race() without comment
kcsan: Add __kcsan_{enable,disable}_current() variants
objtool, kcsan: Add kcsan_disable_current() and kcsan_enable_current_nowarn()
Qiujun Huang (1):
kcsan: Fix a typo in a comment
Wei Yongjun (1):
kcsan: Use GFP_ATOMIC under spin lock
Documentation/dev-tools/kcsan.rst | 228 ++++++++++++-------
include/linux/compiler.h | 4 +-
include/linux/kcsan-checks.h | 261 ++++++++++++++++++----
include/linux/kcsan.h | 19 +-
init/init_task.c | 1 +
kernel/kcsan/atomic.h | 21 +-
kernel/kcsan/core.c | 183 ++++++++++-----
kernel/kcsan/debugfs.c | 47 +++-
kernel/kcsan/kcsan.h | 8 +-
kernel/kcsan/report.c | 455 ++++++++++++++++++++++++--------------
lib/Kconfig.kcsan | 39 +++-
scripts/checkpatch.pl | 8 +
tools/objtool/check.c | 4 +
13 files changed, 880 insertions(+), 398 deletions(-)
reply other threads:[~2020-05-07 23:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200507231227.GA12010@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=elver@google.com \
--cc=hqjagain@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=weiyongjun1@huawei.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 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®