[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+bp7VZDNLk=LKPciBepRTmWza1rKG7bma_xSCD64SY5Aw@mail.gmail.com>
Date: Mon, 15 Jan 2018 14:02:24 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Pavel Machek <pavel@....cz>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Mike Galbraith <efault@....de>,
LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: LKML admins (syzbot emails are not delivered)
On Mon, Jan 15, 2018 at 1:54 PM, Pavel Machek <pavel@....cz> wrote:
> Hi!
>
>> > *Snort*
>> >
>> > If the information to solve an issue is not in the Oops syzbot is
>> > useless.
>>
>> Hi Eric
>>
>> That's true. But maintainers of the subsystem is in the best position
>> to judge that. For that they need to see the report.
>
> Unless they are already overloaded by better quality reports.
>
>> > Further there is no place in the syzbot process to test fixes.
>>
>> Please elaborate.
>> Kernel developer who fixes the bugs, tests it the same way as he/she
>> does for any other bugs. There is really nothing in syzbot that
>> prevents you from testing.
>
> Well, normally people are interested in the bugs they report, and thus
> willing to test the patches. Your bot.. is not interested.
Not true. syzbot is very much interested in bugs it reports, keeps
careful track of them and tests patches.
Powered by blists - more mailing lists