LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Qian Cai <cai@lca.pw>
Cc: Andrey Konovalov <andreyknvl@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v3] kcsan: Add option for verbose reporting
Date: Wed, 15 Apr 2020 15:42:14 -0700 [thread overview]
Message-ID: <20200415224213.GA26058@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <3B06DA7F-DCAF-4566-B72A-F088A8F0B8A9@lca.pw>
On Mon, Apr 06, 2020 at 04:33:27PM -0400, Qian Cai wrote:
>
>
> > On Apr 6, 2020, at 3:51 PM, Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > On Mon, Apr 06, 2020 at 09:45:44AM -0400, Qian Cai wrote:
> >>
> >>
> >>> On Apr 6, 2020, at 9:35 AM, Paul E. McKenney <paulmck@kernel.org> wrote:
> >>>
> >>> It goes back in in seven days, after -rc1 is released. The fact that
> >>> it was there last week was a mistake on my part, and I did eventually
> >>> get my hand slapped for it. ;-)
> >>>
> >>> In the meantime, if it would help, I could group the KCSAN commits
> >>> on top of those in -tip to allow you to get them with one "git pull"
> >>> command.
> >>
> >> Testing Linux-next for a week without that commit with KCSAN is a torture, so please do that if that is not much work. Otherwise, I could manually cherry-pick the commit myself after fixing all the offsets.
> >
> > Just to confirm, you are interested in this -rcu commit, correct?
> >
> > 2402d0eae589 ("kcsan: Add option for verbose reporting")
> >
> > This one and the following are directly on top of the KCSAN stack
> > that is in -tip and thus -next:
> >
> > 48b1fc1 kcsan: Add option to allow watcher interruptions
> > 2402d0e kcsan: Add option for verbose reporting
> > 44656d3 kcsan: Add current->state to implicitly atomic accesses
> > e7b3410 kcsan: Fix a typo in a comment
> > e7325b7 kcsan: Update Documentation/dev-tools/kcsan.rst
> > 1443b8c kcsan: Update API documentation in kcsan-checks.h
> >
> > These are on top of this -tip commit:
> >
> > f5d2313bd3c5 ("kcsan, trace: Make KCSAN compatible with tracing")
> >
> > You can pull them in via the kcsan-dev.2020.03.25a branch if you wish.
>
> Great! That should be enough food for me to survive for this week.
And I just put it back. Please accept my apologies for the delay, but
the branching process fought a bit harder than usual. I probably missed
today's -next, but hopefully tomorrow!
Thanx, Paul
prev parent reply other threads:[~2020-04-15 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 23:10 Marco Elver
2020-02-22 1:36 ` Paul E. McKenney
2020-02-24 19:16 ` Marco Elver
2020-03-01 18:58 ` Paul E. McKenney
2020-04-06 12:59 ` Qian Cai
2020-04-06 13:35 ` Paul E. McKenney
2020-04-06 13:45 ` Qian Cai
2020-04-06 19:51 ` Paul E. McKenney
2020-04-06 20:33 ` Qian Cai
2020-04-15 22:42 ` 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=20200415224213.GA26058@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=andreyknvl@google.com \
--cc=cai@lca.pw \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH v3] kcsan: Add option for verbose reporting' \
/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
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).