From: Florian Westphal <fw@strlen.de>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
outreachy-kernel <outreachy-kernel@googlegroups.com>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH Netfilter] net: netfilter: Replace printk() with more standardize output format.
Date: Sun, 11 Mar 2018 11:55:36 +0100 [thread overview]
Message-ID: <20180311105536.GD11882@breakpoint.cc> (raw)
In-Reply-To: <CA+XqjF_sDve4uztuXD478iOs9xSMqhUcHC5mHZ6O4u-8b-e9QQ@mail.gmail.com>
Arushi Singhal <arushisinghal19971997@gmail.com> wrote:
> I''ll resend the patch according your suggestions.
>
> Just for curiosity wanted to ask why not netdev_*().
netfilter is not a network driver.
> > > register_net_sysctl(net, "net/netfilter", table);
> > > if (!net->ct.event_sysctl_header) {
> > > - printk(KERN_ERR "nf_ct_event: can't register to
> > sysctl.\n");
> > > + netdev_err(net->loopback_dev, "nf_ct_event: can't register
> > to sysctl.\n");
This claims that the error is related to loopback device. Its not.
> > > if (!nskb) {
> > > - printk(KERN_WARNING "nf_queue: OOM "
> > > - "in mangle, dropping packet\n");
> > > + netdev_warn(nskb->dev, "nf_queue: OOM "
> > > + "in mangle, dropping
This now points at a random network device, but again
this condition doesn't have anything to do with a network device.
next prev parent reply other threads:[~2018-03-11 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 18:39 [PATCH Netfilter] net: netfilter: Replace printk() with more standardize output format Arushi Singhal
2018-03-10 19:13 ` Pablo Neira Ayuso
2018-03-11 5:07 ` Arushi Singhal
2018-03-11 10:55 ` Florian Westphal [this message]
2018-03-11 3:41 ` [Outreachy kernel] " Vaishali Thakkar
2018-03-11 4:41 ` Arushi Singhal
2018-03-11 6:44 ` Vaishali Thakkar
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=20180311105536.GD11882@breakpoint.cc \
--to=fw@strlen.de \
--cc=arushisinghal19971997@gmail.com \
--cc=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.