From: "Paul E. McKenney" <paulmck@kernel.org>
To: Qian Cai <cai@lca.pw>
Cc: Marco Elver <elver@google.com>,
John Hubbard <jhubbard@nvidia.com>,
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>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2 5/5] kcsan: Introduce ASSERT_EXCLUSIVE_BITS(var, mask)
Date: Wed, 12 Feb 2020 13:40:29 -0800 [thread overview]
Message-ID: <20200212214029.GS2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <ED2B665D-CF42-45BD-B476-523E3549F127@lca.pw>
On Wed, Feb 12, 2020 at 07:30:16AM -0500, Qian Cai wrote:
>
>
> > On Feb 12, 2020, at 5:57 AM, Marco Elver <elver@google.com> wrote:
> >
> > KCSAN is currently in -rcu (kcsan branch has the latest version),
> > -tip, and -next.
>
> It would like be nice to at least have this patchset can be applied against the linux-next, so I can try it a spin.
>
> Maybe a better question to Paul if he could push all the latest kcsan code base to linux-next soon since we are now past the merging window. I also noticed some data races in rcu but only found out some of them had already been fixed in rcu tree but not in linux-next.
I have pushed all that I have queued other than the last set of five,
which I will do tomorrow (Prague time) if testing goes well.
Could you please check the -rcu "dev" branch to see if I am missing any
of the KCSAN patches?
Thanx, Paul
next prev parent reply other threads:[~2020-02-12 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 16:04 [PATCH v2 1/5] kcsan: Move interfaces that affects checks to kcsan-checks.h Marco Elver
2020-02-11 16:04 ` [PATCH v2 2/5] compiler.h, seqlock.h: Remove unnecessary kcsan.h includes Marco Elver
2020-02-11 16:04 ` [PATCH v2 3/5] kcsan: Introduce kcsan_value_change type Marco Elver
2020-02-11 16:04 ` [PATCH v2 4/5] kcsan: Add kcsan_set_access_mask() support Marco Elver
2020-02-11 16:04 ` [PATCH v2 5/5] kcsan: Introduce ASSERT_EXCLUSIVE_BITS(var, mask) Marco Elver
2020-02-11 21:41 ` John Hubbard
2020-02-12 10:57 ` Marco Elver
2020-02-12 12:30 ` Qian Cai
2020-02-12 21:40 ` Paul E. McKenney [this message]
2020-02-13 0:48 ` Qian Cai
2020-02-13 6:35 ` Paul E. McKenney
2020-02-12 21:36 ` 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=20200212214029.GS2935@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=cai@lca.pw \
--cc=david@redhat.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.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).