From: Stephan Mueller <smueller@chronox.de>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Eric Dumazet <edumazet@google.com>,
Eric Biggers <ebiggers3@gmail.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
andreyknvl <andreyknvl@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
David Miller <davem@davemloft.net>,
Willem de Bruijn <willemb@google.com>,
Guenter Roeck <groeck@google.com>
Subject: Re: [RFC] syzbot process
Date: Thu, 21 Dec 2017 14:36:27 +0100 [thread overview]
Message-ID: <2591445.sHVZGWs4yY@tauon.chronox.de> (raw)
In-Reply-To: <CAPAsAGysymOS0MQQgmX6v3Ft9+z_gDFkWfDTqupT2raAVohN7w@mail.gmail.com>
Am Donnerstag, 21. Dezember 2017, 14:22:40 CET schrieb Andrey Ryabinin:
Hi Andrey,
> 2017-12-21 15:52 GMT+03:00 Dmitry Vyukov <dvyukov@google.com>:
> > Any other proposals, thoughts, ideas?
>
> a) Assume that patches send in replies to the bug report are fixes.
>
> b) Almost the same as your "syzbot-fix: HASH" proposal, but slightly
> closer to normal kernel development workflow.
> Add hash/bug id into the From field of email, i.e.
>
> instead of
> From: syzbot <syzkaller@googlegroups.com>
>
> make it
> From: syzbot-{hash} <syzkaller@googlegroups.com>
>
> And ask to include "Reported-by: syzbot-{hash}
> <syzkaller@googlegroups.com>" tag in a changelog.
>
> a) doesn't exclude b) or "#syz: fix " emails, and vise versa
One additional suggestion: Rerun all already generated reproducer tests on,
say, each updated kernel (e.g. newer rc or even full new version). If an issue
is detected again, send a reply to the original message to indicate that the
issue is still there. Note, I sometimes even fear that a patch that ought to
fix the reported issue may not completely fix it considering races.
The problem with the current approach (at least to me) is that on mailing
lists with some volume, such reports get easily buried.
Ciao
Stephan
next prev parent reply other threads:[~2017-12-21 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 12:52 Dmitry Vyukov
2017-12-21 13:22 ` Andrey Ryabinin
2017-12-21 13:36 ` Stephan Mueller [this message]
2017-12-28 10:19 ` Dmitry Vyukov
2017-12-21 18:08 ` Linus Torvalds
2017-12-28 10:14 ` Dmitry Vyukov
2017-12-28 10:15 ` Dmitry Vyukov
2017-12-21 17:05 ` Greg Kroah-Hartman
2017-12-28 10:23 ` Dmitry Vyukov
2017-12-22 3:32 ` Eric Biggers
2017-12-28 10:41 ` Dmitry Vyukov
2017-12-28 10:51 ` Ozgur
2017-12-28 11:45 ` Dmitry Vyukov
2017-12-28 12:26 ` Ozgur
2017-12-28 12:30 ` Dmitry Vyukov
2017-12-28 12:55 ` Ozgur
2018-01-08 12:51 ` Dmitry Vyukov
2017-12-28 12:27 ` Dmitry Vyukov
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=2591445.sHVZGWs4yY@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=ebiggers3@gmail.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@google.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=ryabinin.a.a@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willemb@google.com \
/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
all inboxes | Powered by JetHome®