From: Mark Rutland <mark.rutland@arm.com>
To: Marco Elver <elver@google.com>
Cc: paulmck@kernel.org, will@kernel.org, dvyukov@google.com,
glider@google.com, boqun.feng@gmail.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] kcsan: Add support for reporting observed value changes
Date: Thu, 15 Apr 2021 12:47:31 +0100 [thread overview]
Message-ID: <20210415114731.GA73625@E107129.arm.com> (raw)
In-Reply-To: <20210414112825.3008667-1-elver@google.com>
On Wed, Apr 14, 2021 at 01:28:16PM +0200, Marco Elver wrote:
> This series adds support for showing observed value changes in reports.
> Several clean up and refactors of KCSAN reporting code are done as a
> pre-requisite.
> This series was originally prepared courtesy of Mark Rutland in
> September 2020.
For anyone looking for the original, it was never posted to a list, but
is sat on my kcsan/rework branch on kernel.org:
https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=kcsan/rework
> Because KCSAN had a few minor changes since the original
> draft of the series, it required a rebase and re-test. To not be
> forgotten and get these changes in sooner than later, Mark kindly agreed
> to me adopting the series and doing the rebase, a few minor tweaks, and
> finally re-test.
Thanks for picking this up!
All your changes look good to me (along with the documentation patch),
so FWIW:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
>
> Marco Elver (1):
> kcsan: Document "value changed" line
>
> Mark Rutland (8):
> kcsan: Simplify value change detection
> kcsan: Distinguish kcsan_report() calls
> kcsan: Refactor passing watchpoint/other_info
> kcsan: Fold panic() call into print_report()
> kcsan: Refactor access_info initialization
> kcsan: Remove reporting indirection
> kcsan: Remove kcsan_report_type
> kcsan: Report observed value changes
>
> Documentation/dev-tools/kcsan.rst | 88 +++++++---------
> kernel/kcsan/core.c | 53 ++++------
> kernel/kcsan/kcsan.h | 39 ++++---
> kernel/kcsan/report.c | 169 ++++++++++++++++--------------
> 4 files changed, 162 insertions(+), 187 deletions(-)
>
> --
> 2.31.1.295.g9ea45b61b8-goog
>
prev parent reply other threads:[~2021-04-15 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 11:28 Marco Elver
2021-04-14 11:28 ` [PATCH 1/9] kcsan: Simplify value change detection Marco Elver
2021-04-14 11:28 ` [PATCH 2/9] kcsan: Distinguish kcsan_report() calls Marco Elver
2021-04-14 11:28 ` [PATCH 3/9] kcsan: Refactor passing watchpoint/other_info Marco Elver
2021-04-14 11:28 ` [PATCH 4/9] kcsan: Fold panic() call into print_report() Marco Elver
2021-04-14 11:28 ` [PATCH 5/9] kcsan: Refactor access_info initialization Marco Elver
2021-04-14 11:28 ` [PATCH 6/9] kcsan: Remove reporting indirection Marco Elver
2021-04-14 11:28 ` [PATCH 7/9] kcsan: Remove kcsan_report_type Marco Elver
2021-04-14 11:28 ` [PATCH 8/9] kcsan: Report observed value changes Marco Elver
2021-04-14 11:28 ` [PATCH 9/9] kcsan: Document "value changed" line Marco Elver
2021-04-15 11:47 ` Mark Rutland [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=20210415114731.GA73625@E107129.arm.com \
--to=mark.rutland@arm.com \
--cc=boqun.feng@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=will@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®