From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752565AbdLUNgg (ORCPT <rfc822;w@1wt.eu>);
        Thu, 21 Dec 2017 08:36:36 -0500
Received: from mail.eperm.de ([89.247.134.16]:44286 "EHLO mail.eperm.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752311AbdLUNga (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 21 Dec 2017 08:36:30 -0500
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
Message-ID: <2591445.sHVZGWs4yY@tauon.chronox.de>
In-Reply-To: <CAPAsAGysymOS0MQQgmX6v3Ft9+z_gDFkWfDTqupT2raAVohN7w@mail.gmail.com>
References: <CACT4Y+bkOpUyjEGUT96T4tPGFeoQ2iP8ZGoE_FMiAg3h5RKxDA@mail.gmail.com> <CAPAsAGysymOS0MQQgmX6v3Ft9+z_gDFkWfDTqupT2raAVohN7w@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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