From: "Paul E. McKenney" <paulmck@kernel.org>
To: Marco Elver <elver@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
kernel-team@fb.com, Ingo Molnar <mingo@kernel.org>,
Andrey Konovalov <andreyknvl@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>, Qian Cai <cai@lca.pw>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: [PATCH kcsan 0/10] KCSAN updates for v5.9
Date: Tue, 23 Jun 2020 09:31:35 -0700 [thread overview]
Message-ID: <20200623163135.GL9247@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CANpmjNO_2N5PB6MOQqEgpwNKmTtLrSNcY+-a2fVncESyjuO=Wg@mail.gmail.com>
On Tue, Jun 23, 2020 at 05:06:26PM +0200, Marco Elver wrote:
> On Tue, 23 Jun 2020 at 15:43, Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > On Tue, Jun 23, 2020 at 08:31:15AM +0200, Marco Elver wrote:
> > > On Tue, 23 Jun 2020 at 02:43, Paul E. McKenney <paulmck@kernel.org> wrote:
> > > >
> > > > Hello!
> > > >
> > > > This series provides KCSAN updates:
> > > >
> > > > 1. Annotate a data race in vm_area_dup(), courtesy of Qian Cai.
> > > >
> > > > 2. x86/mm/pat: Mark an intentional data race, courtesy of Qian Cai.
> > > >
> > > > 3. Add ASSERT_EXCLUSIVE_ACCESS() to __list_splice_init_rcu().
> > > >
> > > > 4. Add test suite, courtesy of Marco Elver.
> > > >
> > > > 5. locking/osq_lock: Annotate a data race in osq_lock.
> > > >
> > > > 6. Prefer '__no_kcsan inline' in test, courtesy of Marco Elver.
> > > >
> > > > 7. Silence -Wmissing-prototypes warning with W=1, courtesy of Qian Cai.
> > > >
> > > > 8. Rename test.c to selftest.c, courtesy of Marco Elver.
> > > >
> > > > 9. Remove existing special atomic rules, courtesy of Marco Elver.
> > > >
> > > > 10. Add jiffies test to test suite, courtesy of Marco Elver.
> > >
> > > Do we want GCC support back for 5.9?
> > >
> > > https://lkml.kernel.org/r/20200618093118.247375-1-elver@google.com
> > >
> > > I was hoping it could go into 5.9, because it makes a big difference
> > > in terms of usability as it provides more compiler choice. The only
> > > significant change for GCC support is the addition of the checking of
> > > (CC_IS_GCC && (....)).
> >
> > Very good, I will rebase the following into the KCSAN branch for v5.9:
> >
> > 3e490e3 kcsan: Re-add GCC as a supported compiler
> > 03296de kcsan: Simplify compiler flags
> > d831090 kcsan: Disable branch tracing in core runtime
> >
> > Please let me know if any other adjustments are needed.
>
> Looks good to me, thank you!
And updated on the "dev" branch of -rcu.
Thanx, Paul
next prev parent reply other threads:[~2020-06-23 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 0:43 [PATCH kcsan 0/10] KCSAN updates for v5.9 Paul E. McKenney
2020-06-23 6:31 ` Marco Elver
2020-06-23 13:43 ` Paul E. McKenney
2020-06-23 15:06 ` Marco Elver
2020-06-23 16:31 ` Paul E. McKenney [this message]
2020-06-24 19:02 ` Paul E. McKenney
2020-06-24 19:03 ` [PATCH kcsan 1/3] kcsan: Re-add GCC as a supported compiler paulmck
2020-06-24 19:03 ` [PATCH kcsan 2/3] kcsan: Simplify compiler flags paulmck
2020-06-24 19:03 ` [PATCH kcsan 3/3] kcsan: Disable branch tracing in core runtime paulmck
2020-06-24 20:08 ` [PATCH kcsan 0/10] KCSAN updates for v5.9 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=20200623163135.GL9247@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=andreyknvl@google.com \
--cc=boqun.feng@gmail.com \
--cc=cai@lca.pw \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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).