From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] tcp: rate limit synflood warnings further Date: Tue, 11 Sep 2018 23:35:03 -0700 (PDT) Message-ID: <20180911.233503.2281697703604725089.davem@davemloft.net> References: <20180909231212.212470-1-willemdebruijn.kernel@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com, willemb@google.com To: willemdebruijn.kernel@gmail.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:57310 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726082AbeILLiG (ORCPT ); Wed, 12 Sep 2018 07:38:06 -0400 In-Reply-To: <20180909231212.212470-1-willemdebruijn.kernel@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Willem de Bruijn Date: Sun, 9 Sep 2018 19:12:12 -0400 > From: Willem de Bruijn > > Convert pr_info to net_info_ratelimited to limit the total number of > synflood warnings. > > Commit 946cedccbd73 ("tcp: Change possible SYN flooding messages") > rate limits synflood warnings to one per listener. > > Workloads that open many listener sockets can still see a high rate of > log messages. Syzkaller is one frequent example. > > Signed-off-by: Willem de Bruijn Applied, thanks Willem. Is this stable material?