From: Patrick McHardy <kaber@trash.net>
To: Cong Wang <cwang@twopensource.com>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Ilia Mirkin <imirkin@alum.mit.edu>,
netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vitaly Lavrov <lve@guap.ru>
Subject: Re: ip_set: protocol %u message -- useful?
Date: Thu, 13 Feb 2014 18:42:54 +0000 [thread overview]
Message-ID: <20140213184254.GF14175@macbook.localnet> (raw)
In-Reply-To: <CAHA+R7MeEEfqz-7RhCUjsoWPx_BKHVXFV3Y32xjf0B1WwjNdRQ@mail.gmail.com>
On Thu, Feb 13, 2014 at 10:32:45AM -0800, Cong Wang wrote:
> On Thu, Feb 13, 2014 at 2:30 AM, Jozsef Kadlecsik
> <kadlec@blackhole.kfki.hu> wrote:
> > On Thu, 13 Feb 2014, Ilia Mirkin wrote:
> >> messages in my dmesg. This might be because of some local
> >> configuration changes I've made, or perhaps a kernel upgrade. Either
> >> way, it appears this message has been a pr_notice since the original
> >> code added it in a7b4f989a62 ("netfilter: ipset: IP set core
> >> support").
> >>
> >> Does this message provide a lot of value? Or could it be made into a pr_debug?
> >
> > That's a report message on the protocol version used by the ipset
> > subsystem. There was (and possibly will be) multiple protocols, so it
> > helps to catch basic userpsace/kernelspace communication issues.
>
> But still it doesn't deserve a pr_notice()... pr_info() should be enough.
Maybe printing "using protocol version X" will make it appear less like
a debugging message referring to packet contents or something similar.
> diff --git a/net/netfilter/ipset/ip_set_core.c
> b/net/netfilter/ipset/ip_set_core.c
> index de770ec..5ea063f 100644
> --- a/net/netfilter/ipset/ip_set_core.c
> +++ b/net/netfilter/ipset/ip_set_core.c
> @@ -1945,7 +1945,7 @@ ip_set_net_init(struct net *net)
> return -ENOMEM;
> inst->is_deleted = 0;
> rcu_assign_pointer(inst->ip_set_list, list);
> - pr_notice("ip_set: protocol %u\n", IPSET_PROTOCOL);
> + pr_info("ip_set: protocol %u\n", IPSET_PROTOCOL);
> return 0;
> }
next prev parent reply other threads:[~2014-02-13 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 9:30 ip_set: protocol %u message -- useful? Ilia Mirkin
2014-02-13 10:30 ` Jozsef Kadlecsik
2014-02-13 18:32 ` Cong Wang
2014-02-13 18:42 ` Patrick McHardy [this message]
2014-02-13 18:58 ` Ilia Mirkin
2014-02-13 19:59 ` Florian Westphal
2014-02-13 20:55 ` Jozsef Kadlecsik
2014-02-13 19:02 ` Joe Perches
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=20140213184254.GF14175@macbook.localnet \
--to=kaber@trash.net \
--cc=cwang@twopensource.com \
--cc=imirkin@alum.mit.edu \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=lve@guap.ru \
--cc=netdev@vger.kernel.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