linux-kernel - Re: LKML admins (syzbot emails are not delivered)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87lggzumfc.fsf@xmission.com>
Date:   Mon, 15 Jan 2018 10:16:55 -0600
From:   ebiederm@...ssion.com (Eric W. Biederman)
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     Pavel Machek <pavel@....cz>, 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)

Dmitry Vyukov <dvyukov@...gle.com> writes:

2> 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.

It offers to test fixes not to add more information so that the bug can
be tracked down better.  Having asked explicitly for some additional
testing to track down and issue and been told the process was happy to
test fixes I know that this has been most definitely the case.

Modifying the kernel and testing is important as sometimes it can be
extremely difficult to figure out what causes an issue.  Especially when
it is an interaction of factors like running a system on the edge of
OOM.  So it requires small kmallocs to fail (which does not usually
happen).

Eric