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 v2 0/2] kcsan: Improvements to reporting
Date: Fri, 10 Jan 2020 21:17:26 -0800 [thread overview]
Message-ID: <20200111051726.GH13449@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200110184834.192636-1-elver@google.com>
On Fri, Jan 10, 2020 at 07:48:32PM +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.
>
> v2:
> * Paul E. McKenney: commit message reword.
> * Use jiffies instead of ktime -- we want to avoid calling into any
> further complex libraries, since KCSAN may also detect data races in
> them, and as a result potentially leading to observing corrupt state
> (e.g. here, observing corrupt ktime_t value).
>
>
> Marco Elver (2):
> kcsan: Show full access type in report
> kcsan: Rate-limit reporting per data races
I replaced the existing commits with these guys, thank you!
Thanx, Paul
> kernel/kcsan/core.c | 15 +++--
> kernel/kcsan/kcsan.h | 2 +-
> kernel/kcsan/report.c | 151 +++++++++++++++++++++++++++++++++++-------
> lib/Kconfig.kcsan | 10 +++
> 4 files changed, 146 insertions(+), 32 deletions(-)
>
> --
> 2.25.0.rc1.283.g88dfdc4193-goog
>
prev parent reply other threads:[~2020-01-11 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 18:48 [PATCH -rcu v2 0/2] kcsan: Improvements to reporting Marco Elver
2020-01-10 18:48 ` [PATCH -rcu v2 1/2] kcsan: Show full access type in report Marco Elver
2020-01-10 18:48 ` [PATCH -rcu v2 2/2] kcsan: Rate-limit reporting per data races Marco Elver
2020-01-11 5:17 ` Paul E. McKenney [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=20200111051726.GH13449@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.