Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753752AbdLUSIy (ORCPT ); Thu, 21 Dec 2017 13:08:54 -0500 Received: from mail-io0-f182.google.com ([209.85.223.182]:39863 "EHLO mail-io0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751705AbdLUSIw (ORCPT ); Thu, 21 Dec 2017 13:08:52 -0500 X-Google-Smtp-Source: ACJfBovMpfiD1nK3J0mjUwLrt9UJ3Qzzm7WqjgSnCALzYM6339iKU5lC0uvyrx8odK7aPwUqoLM86fpI2k/eg+VSkZE= MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Thu, 21 Dec 2017 10:08:51 -0800 X-Google-Sender-Auth: NYAYXHtllM6CwJBc2xC5fWq3OlQ Message-ID: Subject: Re: [RFC] syzbot process To: Andrey Ryabinin Cc: Dmitry Vyukov , LKML , syzkaller , Eric Dumazet , Eric Biggers , Kostya Serebryany , Alexander Potapenko , andreyknvl , Greg Kroah-Hartman , Andrew Morton , Tetsuo Handa , David Miller , Willem de Bruijn , Guenter Roeck , Stephan Mueller Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1180 Lines: 31 On Thu, Dec 21, 2017 at 5:22 AM, Andrey Ryabinin wrote: > > instead of > From: syzbot > > make it > From: syzbot-{hash} That is probably good, but people drop the name all the time. But with a very simple tweak, I think this would be close to perfect: put the hash in the original email instead, and use "+" instead of "-", because that's the standard email ("latter part doesn't matter"). Skip the proper name part entirely, since it doesn't really add anything. And then make it show up in the "Cc:" part or "Reported-by:", so it would just look something like Reported-by: syzkaller+1234abc@googlegroups.com and you're all done. I think that would be easiest for us to track (just one email that we're supposed to put in the commit message _anyway_), and I hope/think that all email clients and servers will still maintain the original full "syzkaller+xyz" part of the email, so it doesn't get lost. Because the "proper name" part definitely does get lost occasionally. I'm not sure why it happens, but it definitely happens quite often. Linus