From: "Paul E. McKenney" <paulmck@kernel.org>
To: Marco Elver <elver@google.com>
Cc: andreyknvl@google.com, glider@google.com, dvyukov@google.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rcu 0/2] kcsan: Improvements to reporting
Date: Thu, 9 Jan 2020 08:27:39 -0800 [thread overview]
Message-ID: <20200109162739.GS13449@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200109152322.104466-1-elver@google.com>
On Thu, Jan 09, 2020 at 04:23:20PM +0100, Marco Elver wrote:
> Improvements to KCSAN data race reporting:
> 1. Show if access is marked (*_ONCE, atomic, etc.).
> 2. Rate limit reporting to avoid spamming console.
>
> Marco Elver (2):
> kcsan: Show full access type in report
> kcsan: Rate-limit reporting per data races
Queued and pushed, thank you! I edited the commit logs a bit, so could
you please check to make sure that I didn't mess anything up?
At some point, boot-time-allocated per-CPU arrays might be needed to
avoid contention on large systems, but one step at a time. ;-)
Thanx, Paul
> kernel/kcsan/core.c | 15 +++--
> kernel/kcsan/kcsan.h | 2 +-
> kernel/kcsan/report.c | 153 +++++++++++++++++++++++++++++++++++-------
> lib/Kconfig.kcsan | 10 +++
> 4 files changed, 148 insertions(+), 32 deletions(-)
>
> --
> 2.25.0.rc1.283.g88dfdc4193-goog
>
next prev parent reply other threads:[~2020-01-09 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 15:23 [PATCH -rcu 0/2] kcsan: Improvements to reporting Marco Elver
2020-01-09 15:23 ` [PATCH -rcu 1/2] kcsan: Show full access type in report Marco Elver
2020-01-09 15:23 ` [PATCH -rcu 2/2] kcsan: Rate-limit reporting per data races Marco Elver
2020-01-10 18:20 ` Marco Elver
2020-01-10 18:54 ` Marco Elver
2020-01-11 5:13 ` Paul E. McKenney
2020-01-09 16:27 ` Paul E. McKenney [this message]
2020-01-09 17:03 ` [PATCH -rcu 0/2] kcsan: Improvements to reporting Marco Elver
2020-01-09 17:31 ` Paul E. McKenney
2020-01-09 17:42 ` Marco Elver
2020-01-09 20:46 ` Paul E. McKenney
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=20200109162739.GS13449@paulmck-ThinkPad-P72 \
--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=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).