From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f175.google.com ([209.85.192.175]:39725 "EHLO mail-pf0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932502AbeBVM7p (ORCPT ); Thu, 22 Feb 2018 07:59:45 -0500 Received: by mail-pf0-f175.google.com with SMTP id c143so2034618pfb.6 for ; Thu, 22 Feb 2018 04:59:45 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20180222100310.GD24858@breakpoint.cc> References: <20180221.164732.52123327250032598.davem@davemloft.net> <1519288016.2583.4.camel@redhat.com> <20180222100310.GD24858@breakpoint.cc> From: Dmitry Vyukov Date: Thu, 22 Feb 2018 13:59:23 +0100 Message-ID: Subject: Re: syzcaller patch postings... To: Florian Westphal Cc: Paolo Abeni , David Miller , syzkaller-bugs@googlegroups.com, netdev Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Feb 22, 2018 at 11:03 AM, Florian Westphal wrote: > Dmitry Vyukov wrote: >> 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. > > Yes, thats at least my expected/desired behaviour. > This way I can even CC some other person (maintainer, reporter etc) > to have them informed about test result too. > >> I will go and fix it now. > > Thank you Dmitry! This now should be fixed by https://github.com/google/syzkaller/commit/7daaa06d53f0f496aa1a87656d16c81ebff37f73 I've also added a note to the doc referenced from bug report emails: https://github.com/google/syzkaller/commit/7daaa06d53f0f496aa1a87656d16c81ebff37f73#diff-5b3b5ff5f03b01e1d31ec93aafd2f3d5