From: Daniel Borkmann <dborkman@redhat.com>
To: roy.qing.li@gmail.com
Cc: netdev@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH][net-next] tcp: remove the duplicate prefixes in the logging message
Date: Wed, 23 Apr 2014 11:35:57 +0200 [thread overview]
Message-ID: <5357897D.8060809@redhat.com> (raw)
In-Reply-To: <1398245335-18780-1-git-send-email-roy.qing.li@gmail.com>
On 04/23/2014 11:28 AM, roy.qing.li@gmail.com wrote:
> From: Li RongQing <roy.qing.li@gmail.com>
>
> The current message is:
> TCP: TCP: Possible SYN flooding on port 80. Sending cookies. ...
>
> The cause is that pr_info will implicitly print the pr_fmt string, which is standard
> prefix, and explicitly print the "proto" which is "TCP:" too
>
> it is unsuitable to not print proto, since proto maybe TCPv6, so use printk directly.
Can't you just leave the pr_info() instead, and reword that into something like:
"Possible %s SYN flooding[...]", proto
> Cc: Joe Perches <joe@perches.com>
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
> ---
> net/ipv4/tcp_ipv4.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
> index 438f3b9..85ebe68 100644
> --- a/net/ipv4/tcp_ipv4.c
> +++ b/net/ipv4/tcp_ipv4.c
> @@ -892,8 +892,8 @@ bool tcp_syn_flood_action(struct sock *sk,
> lopt = inet_csk(sk)->icsk_accept_queue.listen_opt;
> if (!lopt->synflood_warned && sysctl_tcp_syncookies != 2) {
> lopt->synflood_warned = 1;
> - pr_info("%s: Possible SYN flooding on port %d. %s. Check SNMP counters.\n",
> - proto, ntohs(tcp_hdr(skb)->dest), msg);
> + printk(KERN_INFO "%s: Possible SYN flooding on port %d. %s. Check SNMP counters.\n",
> + proto, ntohs(tcp_hdr(skb)->dest), msg);
> }
> return want_cookie;
> }
>
next prev parent reply other threads:[~2014-04-23 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 9:28 [PATCH][net-next] tcp: remove the duplicate prefixes in the logging message roy.qing.li
2014-04-23 9:35 ` Daniel Borkmann [this message]
2014-04-23 13:32 ` Li RongQing
2014-04-24 17:26 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 13:17 roy.qing.li
2014-04-22 0:04 ` Li RongQing
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=5357897D.8060809@redhat.com \
--to=dborkman@redhat.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=roy.qing.li@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).