[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221110153901.7daa86e1@hermes.local>
Date: Thu, 10 Nov 2022 15:39:01 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Jamie Bainbridge <jamie.bainbridge@...il.com>
Cc: Eric Dumazet <edumazet@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tcp: Add listening address to SYN flood message
On Thu, 10 Nov 2022 21:21:06 +1100
Jamie Bainbridge <jamie.bainbridge@...il.com> wrote:
> + xchg(&queue->synflood_warned, 1) == 0) {
> +#if IS_ENABLED(CONFIG_IPV6)
> + if (sk->sk_family == AF_INET6) {
> + net_info_ratelimited("%s: Possible SYN flooding on port %d. IP %pI6c. %s. Check SNMP counters.\n",
> + proto, sk->sk_num,
> + &sk->sk_v6_rcv_saddr, msg);
> + } else
> +#endif
> + {
> + net_info_ratelimited("%s: Possible SYN flooding on port %d. IP %pI4. %s. Check SNMP counters.\n",
> + proto, sk->sk_num, &sk->sk_rcv_saddr, msg);
> + }
> + }
>
Port number is unsigned not signed.
Message also seems overly wordy to me.
Powered by blists - more mailing lists