From: Andrew Lunn <andrew@lunn.ch>
To: Jamie Bainbridge <jamie.bainbridge@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcp: Add listening address to SYN flood message
Date: Thu, 10 Nov 2022 14:51:01 +0100 [thread overview]
Message-ID: <Y20Bxc1gQ8nrFsvA@lunn.ch> (raw)
In-Reply-To: <f847459dc0a0e2d8ffa1d290d06e0e4a226a6f39.1668075479.git.jamie.bainbridge@gmail.com>
On Thu, Nov 10, 2022 at 09:21:06PM +1100, Jamie Bainbridge wrote:
> The SYN flood message prints the listening port number, but on a system
> with many processes bound to the same port on different IPs, it's
> impossible to tell which socket is the problem.
>
> Add the listen IP address to the SYN flood message. It might have been
> nicer to print the address first, but decades of monitoring tools are
> watching for the string "SYN flooding on port" so don't break that.
>
> Tested with each protcol's "any" address and a host address:
>
> Possible SYN flooding on port 9001. IP 0.0.0.0.
> Possible SYN flooding on port 9001. IP 127.0.0.1.
> Possible SYN flooding on port 9001. IP ::.
> Possible SYN flooding on port 9001. IP fc00::1.
>
> Signed-off-by: Jamie Bainbridge <jamie.bainbridge@gmail.com>
> ---
> net/ipv4/tcp_input.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
> index 0640453fce54b6daae0861d948f3db075830daf6..fb86056732266fedc8ad574bbf799dbdd7a425a3 100644
> --- a/net/ipv4/tcp_input.c
> +++ b/net/ipv4/tcp_input.c
> @@ -6831,9 +6831,19 @@ static bool tcp_syn_flood_action(const struct sock *sk, const char *proto)
> __NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPREQQFULLDROP);
>
> if (!queue->synflood_warned && syncookies != 2 &&
> - xchg(&queue->synflood_warned, 1) == 0)
> - net_info_ratelimited("%s: Possible SYN flooding on port %d. %s. Check SNMP counters.\n",
> - proto, sk->sk_num, msg);
> + xchg(&queue->synflood_warned, 1) == 0) {
> +#if IS_ENABLED(CONFIG_IPV6)
> + if (sk->sk_family == AF_INET6) {
Can the IS_ENABLED() go inside the if? You get better build testing
that way.
Andrew
next prev parent reply other threads:[~2022-11-10 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 10:21 [PATCH] tcp: Add listening address to SYN flood message Jamie Bainbridge
2022-11-10 13:51 ` Andrew Lunn [this message]
2022-11-10 21:20 ` Jamie Bainbridge
2022-11-10 22:30 ` Andrew Lunn
2022-11-15 10:29 ` Geert Uytterhoeven
2022-11-10 23:39 ` Stephen Hemminger
2022-11-10 23:46 ` Eric Dumazet
2022-11-11 0:38 ` Jamie Bainbridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y20Bxc1gQ8nrFsvA@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jamie.bainbridge@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox