From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: 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: Mon, 15 Jan 2018 14:53:27 +0100 [thread overview]
Message-ID: <20180115135327.GA2206@amd> (raw)
In-Reply-To: <CACT4Y+Y2ObijZ7Qbb3H6r6kYc-b0z=gc=psHZ8hD1zByR-bqRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
Hi!
> >> In lots of cases (~50%) quality of syzbot reports is equal to human
> >> reports, or _higher_.
> >> It provides exact kernel commit, config, compiler, stand-alone C
> >> reproducer and a nice, symbolized report even with inline frames. You
> >> don't always get all of this from human reports.
> >>
> >> In the remaining cases (no reproducer), quality of syzbot reports is
> >> the _same_ as for human reports.
> >> Say, your machine randomly crashes. You reboot it, but it crashes
> >> again after some time. You try to repeat what you did before the crash
> >> (say, opened a particular web page), but it does not reproduce the
> >> crash. But one way or another, it happened and it's a kernel bug
> >
> > I have not seen a good quality report from syzbot, yet.
>
> I don't know how many you checked, so I don't know how to interpret this.
> If you want to see one, grep kernel commit log for syzbot, get bug id,
> search for it in
> https://groups.google.com/forum/#!forum/syzkaller-bugs
>
>
> > Normally, humans agregate test reports, and test patches etc. Can you
> > step between robot and lkml, and provide same services humans usually
> > provide?
>
> syzbot does all of this already.
Does it? Because its documentation says otherwise:
syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email
with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply
with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email
body.
_You_ should be doing duplicates processing, and preferably you should
also take care to translate replies into something syzbot
understand. Reports should come from your email adress, and you should
really handle replies that do not come in required format.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-01-15 13:53 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 [this message]
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
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=20180115135327.GA2206@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox