[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+ZF_wGDG8-3J4MPMTeNaL0tTARjtktJPC3bJRDd4aODqQ@mail.gmail.com>
Date: Mon, 8 Jan 2018 13:11:49 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: "Theodore Ts'o" <tytso@....edu>,
Dmitry Vyukov <dvyukov@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
syzkaller <syzkaller@...glegroups.com>,
David Miller <davem@...emloft.net>
Subject: Re: LKML admins (syzbot emails are not delivered)
On Fri, Jan 5, 2018 at 12:50 AM, Theodore Ts'o <tytso@....edu> wrote:
> It also seems to me, looking at other complaints on this thread, that
> there is the opportunity for the syzbot to do much more. For example,
> you can see if it repro's on the last released mainline kernel (such
> as 4.14) and if so, have the syzbot automatically do a bisection
> search, so you can make sure the report goes to the best set of
> developers to fix it, a pointer to the guilty commit.
Hi Ted,
I've filed https://github.com/google/syzkaller/issues/501 for this as
this come up several times. There is bunch of problems, though:
- unreliable reproducers
- triggering of unrelated bugs (happens frequently)
- flakes (bugs in GCE, crashes in tty on first ssh connection, etc)
- bugs (races) that manifest in multiple different ways
- bugs that will be attributed to tools improvements (e.g. KASAN,
fault injection improvements)
- reproducers that need slight changes on different kernel revisions
Not sure what quality of bisection we can achieve. And kernel
developers tend to be negative to any kind of bot gaffe, so we can
lose both ways.
Powered by blists - more mailing lists