From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Dmitry Vyukov <dvyukov@google.com>,
"Theodore Ts'o" <tytso@mit.edu>, Pavel Machek <pavel@ucw.cz>,
Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: LKML admins (syzbot emails are not delivered)
Date: Wed, 24 Jan 2018 11:06:02 -0600 [thread overview]
Message-ID: <87y3knyyo5.fsf@xmission.com> (raw)
In-Reply-To: <20180124160438.0da2b219@alans-desktop> (Alan Cox's message of "Wed, 24 Jan 2018 16:04:38 +0000")
Alan Cox <gnomes@lxorguk.ukuu.org.uk> writes:
> On Tue, 16 Jan 2018 09:34:01 +0100
> Dmitry Vyukov <dvyukov@google.com> wrote:
>
>> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o <tytso@mit.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.
Eric
next prev parent reply other threads:[~2018-01-24 17:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:09 LKML admins (syzbot emails are not delivered) Dmitry Vyukov
2018-01-04 9:23 ` Greg Kroah-Hartman
2018-01-04 9:56 ` Ozgur
2018-01-04 15:31 ` David Miller
2018-01-04 19:11 ` Ozgur
2018-01-04 11:03 ` Dmitry Vyukov
2018-01-04 11:04 ` Dmitry Vyukov
2018-01-04 11:20 ` Greg Kroah-Hartman
2018-01-04 15:35 ` David Miller
2018-01-15 9:43 ` Dmitry Vyukov
2018-03-01 16:22 ` Dmitry Vyukov
2018-03-08 20:03 ` David Miller
2018-03-12 8:56 ` Dmitry Vyukov
2018-03-12 14:03 ` David Miller
2018-01-04 23:50 ` Theodore Ts'o
2018-01-08 12:01 ` Dmitry Vyukov
2018-01-08 12:11 ` Dmitry Vyukov
2018-01-04 9:25 ` Pavel Machek
2018-01-04 9:38 ` Mike Galbraith
2018-01-04 9:56 ` Pavel Machek
2018-01-04 11:09 ` Dmitry Vyukov
2018-01-04 11:18 ` Pavel Machek
2018-01-15 10:08 ` Dmitry Vyukov
2018-01-15 13:08 ` Pavel Machek
2018-01-15 13:38 ` Dmitry Vyukov
2018-01-15 13:53 ` Pavel Machek
2018-01-04 15:23 ` Eric W. Biederman
2018-01-15 10:54 ` Dmitry Vyukov
2018-01-15 12:54 ` Pavel Machek
2018-01-15 13:02 ` Dmitry Vyukov
2018-01-15 16:16 ` Eric W. Biederman
2018-01-16 18:01 ` Dmitry Vyukov
2018-01-15 16:38 ` Eric W. Biederman
2018-01-16 7:12 ` Theodore Ts'o
2018-01-16 7:51 ` Dmitry Vyukov
2018-01-16 9:52 ` Guenter Roeck
2018-01-16 9:56 ` Dmitry Vyukov
2018-01-16 9:58 ` Guenter Roeck
2018-01-16 7:59 ` Dmitry Vyukov
2018-01-16 11:19 ` Fengguang Wu
2018-01-16 8:31 ` Dmitry Vyukov
2018-01-16 23:13 ` Theodore Ts'o
2018-01-17 8:06 ` Dmitry Vyukov
2018-01-17 16:53 ` Theodore Ts'o
2018-01-17 17:16 ` Dmitry Vyukov
2018-01-17 22:27 ` Bernd Petrovitsch
2018-01-16 8:34 ` Dmitry Vyukov
2018-01-24 16:04 ` Alan Cox
2018-01-24 17:06 ` Eric W. Biederman [this message]
2018-01-24 17:32 ` Greg Kroah-Hartman
2018-01-16 18:20 ` Dmitry Vyukov
2018-01-17 8:13 ` Dmitry Vyukov
2018-01-04 21:38 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3knyyo5.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=efault@gmx.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.