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,
cai@lca.pw, boqun.feng@gmail.com
Subject: [GIT PULL] KCSAN changes for v5.16
Date: Thu, 11 Nov 2021 08:20:05 -0800 [thread overview]
Message-ID: <20211111162005.GA305579@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Linus,
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/kcsan.2021.11.11a
for you to fetch changes up to ac20e39e8d254da3f82b5ed2afc7bb1e804d32c9:
kcsan: selftest: Cleanup and add missing __init (2021-09-13 16:41:20 -0700)
----------------------------------------------------------------
KCSAN pull request for v5.16
This series contains initialization fixups, testing improvements, addition
of instruction pointer to data-race reports, and scoped data-race checks.
----------------------------------------------------------------
Marco Elver (9):
kcsan: test: Defer kcsan_test_init() after kunit initialization
kcsan: test: Use kunit_skip() to skip tests
kcsan: test: Fix flaky test case
kcsan: Add ability to pass instruction pointer of access to reporting
kcsan: Save instruction pointer for scoped accesses
kcsan: Start stack trace with explicit location if provided
kcsan: Support reporting scoped read-write access type
kcsan: Move ctx to start of argument list
kcsan: selftest: Cleanup and add missing __init
include/linux/kcsan-checks.h | 3 ++
kernel/kcsan/core.c | 75 ++++++++++++++++++++++++------------------
kernel/kcsan/kcsan.h | 8 ++---
kernel/kcsan/kcsan_test.c | 62 +++++++++++++++++++++++------------
kernel/kcsan/report.c | 77 ++++++++++++++++++++++++++++++++++++--------
kernel/kcsan/selftest.c | 72 +++++++++++++++++------------------------
6 files changed, 186 insertions(+), 111 deletions(-)
next reply other threads:[~2021-11-11 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 16:20 Paul E. McKenney [this message]
2021-11-11 23:09 ` 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=20211111162005.GA305579@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=andreyknvl@google.com \
--cc=boqun.feng@gmail.com \
--cc=cai@lca.pw \
--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®