From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f50.google.com ([74.125.83.50]:42521 "EHLO mail-pg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752644AbeBVJ62 (ORCPT ); Thu, 22 Feb 2018 04:58:28 -0500 Received: by mail-pg0-f50.google.com with SMTP id y8so1817660pgr.9 for ; Thu, 22 Feb 2018 01:58:28 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1519288016.2583.4.camel@redhat.com> References: <20180221.164732.52123327250032598.davem@davemloft.net> <1519288016.2583.4.camel@redhat.com> From: Dmitry Vyukov Date: Thu, 22 Feb 2018 10:58:07 +0100 Message-ID: Subject: Re: syzcaller patch postings... To: Paolo Abeni , David Miller Cc: syzkaller-bugs@googlegroups.com, netdev , Florian Westphal Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org List-ID: 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. 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.