From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([184.105.139.130]:47122 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932623AbeBVOfW (ORCPT ); Thu, 22 Feb 2018 09:35:22 -0500 Date: Thu, 22 Feb 2018 09:35:16 -0500 (EST) Message-Id: <20180222.093516.144747386298055475.davem@davemloft.net> To: dvyukov@google.com Cc: pabeni@redhat.com, syzkaller-bugs@googlegroups.com, netdev@vger.kernel.org, fw@strlen.de Subject: Re: syzcaller patch postings... From: David Miller In-Reply-To: References: <20180221.164732.52123327250032598.davem@davemloft.net> <1519288016.2583.4.camel@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: From: Dmitry Vyukov Date: Thu, 22 Feb 2018 10:58:07 +0100 > 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. I don't want syzbot to send the patch to netdev, even if it was in the CC: list. And again this goes for netfilter-devel and linux-wireless as well. There is no reason whatsoever for syzbot to ever post an already posted patch back to the list again, even if it was on the CC: list. In fact netdev will be on that CC: list most of the time.