[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+YUFbbQgE9C1awsVVBFOjLbTXANRQwPK+R58FLjhTb-Vg@mail.gmail.com>
Date: Mon, 16 Apr 2018 13:15:58 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Eric Biggers <ebiggers3@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: syzbot dashboard
On Sat, Apr 14, 2018 at 8:25 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> Coming back to this now that the merge window is almost over ]
>
> On Mon, Mar 26, 2018 at 1:46 AM, Dmitry Vyukov <dvyukov@...gle.com> wrote:
>>
>> I've switched emails to links instead of attachments, here are few
>> recent examples:
>> https://lkml.org/lkml/2018/3/25/31
>> https://lkml.org/lkml/2018/3/25/256
>> https://lkml.org/lkml/2018/3/25/257
>
> Looks good to me. I notice that only the last one got any replies, though.
>
> I wonder if some people auto-ignore the new reports because of having
> been burned by the previous "huge illegible emails" issue.
>
> I do see syzbot fixes in rdma, though, just not for that
> cma_listen_on_all issue. So maybe that bug is nastier.
"possible deadlock in handle_rx" is now marked as fixed with
"vhost_net: add missing lock nesting notation".
"KASAN: use-after-free Read in pppol2tp_connect (3)" is marked as
fixed with "l2tp: fix races in tunnel creation".
"KASAN: use-after-free Read in __list_add_valid (5)" is still open.
Though, there are still 182 open bugs on dashboard:
https://syzkaller.appspot.com/
80+ have reproducers and happened last time recently enough. Few
dozens without reproducers, but as history shows ~2/3 of them are
fixable. Part of the remaining ones is probably fixed, but nobody told
syzbot about the fixes. Part is probably still unfixed but happen
episodically.
Powered by blists - more mailing lists