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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20180124173222.GH16646@kroah.com>
Date:   Wed, 24 Jan 2018 18:32:22 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
Cc:     Alan Cox <gnomes@...rguk.ukuu.org.uk>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Theodore Ts'o <tytso@....edu>, Pavel Machek <pavel@....cz>,
        Mike Galbraith <efault@....de>,
        LKML <linux-kernel@...r.kernel.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 Wed, Jan 24, 2018 at 11:06:02AM -0600, Eric W. Biederman wrote:
> Alan Cox <gnomes@...rguk.ukuu.org.uk> writes:
> 
> > On Tue, 16 Jan 2018 09:34:01 +0100
> > Dmitry Vyukov <dvyukov@...gle.com> wrote:
> >
> >> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o <tytso@....edu> wrote:
> >> >> Outside of the bugs being considered as considered as security issues,
> >> >> the bugs syzbot finds are generally things that don't affect anyone in
> >> >> practice.  So are very low on the priority of things to get fixed.  
> >> 
> >> Not sure why are you saying this, but syzbot has found lots of
> >> hundreds of use-after-free's, out-of-bounds, information leaks,
> >> deadlocks, vm escapes, etc. They have very direct stability and
> >> security impact.
> >
> > Agreed - there may be some UI and presentation issues but it's found some
> > really nasty little bugs.
> 
> I am not certain it has always really found the bugs it hits.
> 
> My experience tends towards a bug report with too little information
> in the Oops to guess what went wrong, that I can not reproduce the
> issue locally, that the no can reproduce, that was produced on a weird
> tree, and with a reporter telling you they are only interested in
> testing fixes.
> 
> Which is a long way of saying if the UI issues are bad enough the issue
> can not be identified in the code I am not certain we have actually
> found a bug.
> 
> So while I can see lots of potential in syzbot.  I can't say if the it
> is greater potential to get bugs fixed or to annoy developers with
> complaints they can't do anything about.

I'm with Alan here, syzbot has found lots of nasty bugs in the areas of
the kernel I maintain.  Many of which are still on my TODO list to fix :)

So yes, it's annoying to me at times as well, but it is good work here,
and I hope to see it continue.

greg k-h