From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f46.google.com ([209.85.160.46]:36116 "EHLO mail-pl0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753843AbeBVNbi (ORCPT ); Thu, 22 Feb 2018 08:31:38 -0500 Received: by mail-pl0-f46.google.com with SMTP id v3so2870209plg.3 for ; Thu, 22 Feb 2018 05:31:38 -0800 (PST) From: Daniel Axtens To: Dmitry Vyukov , Paolo Abeni , David Miller Cc: syzkaller-bugs@googlegroups.com, netdev , Florian Westphal Subject: Re: syzcaller patch postings... In-Reply-To: References: <20180221.164732.52123327250032598.davem@davemloft.net> <1519288016.2583.4.camel@redhat.com> Date: Fri, 23 Feb 2018 00:31:33 +1100 Message-ID: <87mv01i216.fsf@linkitivity.dja.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: netdev-owner@vger.kernel.org List-ID: Dmitry Vyukov writes: > On Thu, Feb 22, 2018 at 9:26 AM, Paolo Abeni wrote: >> On Wed, 2018-02-21 at 16:47 -0500, David Miller wrote: >>> I have to mention this now before it gets out of control. >>> >>> I would like to ask that syzkaller stop posting the patch it is >>> testing when it posts to netdev. >> >> There is an open issue on this topic: >> >> https://github.com/google/syzkaller/issues/526 >> >> The current behaviour is that syzbot replies to all get_maintainer.pl >> recipients after testing a patch, regardless of the test submission >> recipient list, the idea was instead to respect such list. > > > Hi David, Florian, Paolo, > > Didn't realize it triggers patchwork. This wasn't intentional, sorry. A little-publicised and incorrectly-documented(!) feature of Patchwork is that it supports some email headers. In particular, if you include an "X-Patchwork-Hint: ignore" header, the mail will not be parsed by Patchwork. This will stop it being recorded as a patch. Unfortunately it will also stop it being recorded as a comment - I don't know if that's an issue in this case. Maybe we can set you up with Patchwork 2's new checks infrastructure instead. > > Do I understand it correctly that if syzbot replies to the CC list > that was in the testing request, it will resolve the problem? So if > netdev wasn't in CC, it will not be added to CC. > > I will go and fix it now.