Received-SPF: pass (google.com: domain of linux-kernel+bounces-16545-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Thu, 4 Jan 2024 11:55:44 +0100 (CET)
From: Christian Kujau <lists@nerdbynature.de>
To: linux-kernel@vger.kernel.org
cc: netdev@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>, 
    Francesco Ruggeri <fruggeri@arista.com>, 
    Salam Noureddine <noureddine@arista.com>, Dmitry Safonov <dima@arista.com>, 
    David Ahern <dsahern@kernel.org>
Subject: syslog spam: TCP segment has incorrect auth options set
Message-ID: <f6b59324-1417-566f-a976-ff2402718a8d@nerdbynature.de>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Ever since commit 2717b5adea9e ("net/tcp: Add tcp_hash_fail() ratelimited 
logs") the following is printed, in waves of small floods, to syslog:

 kernel: TCP: TCP segment has incorrect auth options set for XX.20.239.12.54681->XX.XX.90.103.80 [S]

This host is connected to the open internet and serves as a small HTTP and 
SSH login server, not much traffic is happening here. So I'd assume these 
messages to be the result of random internet scans and/or fingerprinting 
attempts or the like. While not really a concern, these messages are 
flooding the dmesg buffer over time :-(

Is there a way to adjust the severity of these messages?

* In include/net/tcp.h this gets logged with tcp_hash_fail(), which is
* defined in include/net/tcp_ao.h and calls net_info_ratelimited(), which
* is in turn defined in include/linux/net.h and calls pr_info().

Can e.g. net_dbg_ratelimited be used instead?

Thanks,
Christian.
-- 
BOFH excuse #78:

Yes, yes, its called a design limitation