netdev - Re: syzcaller patch postings...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180222.093516.144747386298055475.davem@davemloft.net>
Date:   Thu, 22 Feb 2018 09:35:16 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     dvyukov@...gle.com
Cc:     pabeni@...hat.com, syzkaller-bugs@...glegroups.com,
        netdev@...r.kernel.org, fw@...len.de
Subject: Re: syzcaller patch postings...

From: Dmitry Vyukov <dvyukov@...gle.com>
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.