Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH v2 5/5] kcsan: Introduce ASSERT_EXCLUSIVE_BITS(var, mask)
Date:   Wed, 12 Feb 2020 07:30:16 -0500
Message-Id: <ED2B665D-CF42-45BD-B476-523E3549F127@lca.pw>
References: <CANpmjNOWzWB2GgJiZx7c96qoy-e+BDFUx9zYr+1hZS1SUS7LBQ@mail.gmail.com>
Cc:     John Hubbard <jhubbard@nvidia.com>,
        "Paul E. McKenney" <paulmck@kernel.org>,
        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>
In-Reply-To: <CANpmjNOWzWB2GgJiZx7c96qoy-e+BDFUx9zYr+1hZS1SUS7LBQ@mail.gmail.com>
To:     Marco Elver <elver@google.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Feb 12, 2020, at 5:57 AM, Marco Elver <elver@google.com> wrote:
>=20
> 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 t=
he linux-next, so I can try it a spin.

Maybe a better question to Paul if he could push all the latest kcsan code b=
ase to linux-next soon since we are now past the merging window. I also noti=
ced some data races in rcu but only found out some of them had already been f=
ixed in rcu tree but not in linux-next.=