linux-kernel - Re: [PATCH v2 5/5] kcsan: Introduce ASSERT_EXCLUSIVE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <79934F2A-E151-480F-B1B1-1C713F932CEC@lca.pw>
Date:   Wed, 12 Feb 2020 19:48:15 -0500
From:   Qian Cai <cai@....pw>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     Marco Elver <elver@...gle.com>, John Hubbard <jhubbard@...dia.com>,
        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 4:40 PM, Paul E. McKenney <paulmck@...nel.org> wrote:
> 
> On Wed, Feb 12, 2020 at 07:30:16AM -0500, Qian Cai wrote:
>> 
>> 
>>> 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.
> 
> 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?

Nope. It looks good to me.