From: Marco Elver <elver@google.com>
To: elver@google.com, paulmck@kernel.org
Cc: mark.rutland@arm.com, dvyukov@google.com, glider@google.com,
boqun.feng@gmail.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] kcsan: Cleanups and fix reporting for scoped accesses
Date: Mon, 9 Aug 2021 13:25:08 +0200 [thread overview]
Message-ID: <20210809112516.682816-1-elver@google.com> (raw)
This series contains several test fixes and cleanups, as well as fixing
reporting for scoped accesses.
Thus far, scoped accesses' stack traces could point anywhere in the
scope, and can be quite confusing when searching for the relevant access
scope several stack frames down. This is fixed by using the original
instruction pointer of the location where the scoped access was set up.
There are more changes coming that depend on the fixed reporting, but it
made more sense to detach the changes in this series as they are useful
on their own and only touch core KCSAN code.
Marco Elver (8):
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
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 ++++++++++++++++++++++++++++++------
5 files changed, 156 insertions(+), 69 deletions(-)
--
2.32.0.605.g8dce9f2422-goog
next reply other threads:[~2021-08-09 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 11:25 Marco Elver [this message]
2021-08-09 11:25 ` [PATCH 1/8] kcsan: test: Defer kcsan_test_init() after kunit initialization Marco Elver
2021-08-09 11:25 ` [PATCH 2/8] kcsan: test: Use kunit_skip() to skip tests Marco Elver
2021-08-09 11:25 ` [PATCH 3/8] kcsan: test: Fix flaky test case Marco Elver
2021-08-09 11:25 ` [PATCH 4/8] kcsan: Add ability to pass instruction pointer of access to reporting Marco Elver
2021-08-09 11:25 ` [PATCH 5/8] kcsan: Save instruction pointer for scoped accesses Marco Elver
2021-08-09 11:25 ` [PATCH 6/8] kcsan: Start stack trace with explicit location if provided Marco Elver
2021-08-09 11:25 ` [PATCH 7/8] kcsan: Support reporting scoped read-write access type Marco Elver
2021-08-09 11:25 ` [PATCH 8/8] kcsan: Move ctx to start of argument list Marco Elver
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=20210809112516.682816-1-elver@google.com \
--to=elver@google.com \
--cc=boqun.feng@gmail.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@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
all inboxes | Powered by JetHome®