[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9oPGnAQ23ZGGJg+ZZRDjG8M+hkqvTko1Zkrc5+zQYUvVg@mail.gmail.com>
Date: Tue, 8 Feb 2022 01:36:19 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Marco Elver <elver@...gle.com>
Cc: Jann Horn <jannh@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>, pmenzel@...gen.mpg.de,
"Theodore Y. Ts'o" <tytso@....edu>,
LKML <linux-kernel@...r.kernel.org>,
Dominik Brodowski <linux@...inikbrodowski.net>
Subject: Re: BUG: KCSAN: data-race in add_device_randomness+0x20d/0x290
Hi Marco,
On 2/8/22, Marco Elver <elver@...gle.com> wrote:
> Jason - if you're interested in KCSAN data race reports in some
> subsystems you maintain (I see a few in Wireguard), let me know, and
> I'll release them from syzbot's moderation queue. The way we're trying
> to do it with KCSAN is that we pre-moderate and ask maintainers if
> they're happy to be forwarded all reports that syzbot finds (currently
> some Networking and RCU, though the latter finds almost all data races
> via KCSAN-enabled rcutorture).
Oh that'd be great. Please feel free to forward whatever for WireGuard
or random.c to jason@...c4.com and I'll gladly try to fix what needs
fixing.
Jason
Powered by blists - more mailing lists