[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <ED2B665D-CF42-45BD-B476-523E3549F127@lca.pw>
Date: Wed, 12 Feb 2020 07:30:16 -0500
From: Qian Cai <cai@....pw>
To: Marco Elver <elver@...gle.com>
Cc: John Hubbard <jhubbard@...dia.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Andrey Konovalov <andreyknvl@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH v2 5/5] kcsan: Introduce ASSERT_EXCLUSIVE_BITS(var, mask)
> On Feb 12, 2020, at 5:57 AM, Marco Elver <elver@...gle.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.
Powered by blists - more mailing lists