From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Jan Engelhardt <jengelh@medozas.de>,
David Miller <davem@davemloft.net>,
ajax@redhat.com, linux-kernel@vger.kernel.org, davej@redhat.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] net: Remove a noisy printk
Date: Mon, 15 Dec 2008 14:32:46 +0100 [thread overview]
Message-ID: <49465C7E.8050103@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0812151419380.4114@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Mon, 15 Dec 2008, Patrick McHardy wrote:
>
>> I agree that it doesn't belong to the generic networking code.
>> But the way its handled in netfilter is far from perfect as well.
>> Currently multiple modules will spam the ringbuffer repeatedly,
>> but offer no possibility to change anything in the behaviour of
>> how these packets are treated. Unfortunately we can't handle this
>> in the ruleset (which is exactly the reason why we're spamming
>> the ringbuffer), so how about we add a module option controlling
>> how to treat those packets and remove the printk?
>
> How about this: let the printk be removed from conntrack and the mangle
> table but put (back) into the filter table with a module option, which
> controls the behaviour (drop/accept & log/nolog)?
Sounds fine to me. We can't log it in the usual way though
(ipt_LOG/nfnetlink_log) and spamming the ringbuffer should
really be a last resort, so I'd prefer to limit it to print
the message exactly once.
next prev parent reply other threads:[~2008-12-15 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1229033625-30825-1-git-send-email-ajax@redhat.com>
2008-12-12 4:32 ` [PATCH] net: Remove a noisy printk David Miller
2008-12-13 22:13 ` Jan Engelhardt
2008-12-14 17:09 ` Jozsef Kadlecsik
2008-12-14 18:06 ` Jan Engelhardt
2008-12-14 20:15 ` Jozsef Kadlecsik
2008-12-15 12:23 ` Patrick McHardy
2008-12-15 13:25 ` Jozsef Kadlecsik
2008-12-15 13:32 ` Patrick McHardy [this message]
2008-12-14 20:03 ` Dave Jones
2008-12-16 19:59 ` Jozsef Kadlecsik
2008-12-16 20:03 ` Jan Engelhardt
2008-12-16 20:00 ` Jan Engelhardt
2008-12-17 8:26 ` Jozsef Kadlecsik
2008-12-19 1:21 ` Rusty Russell
2009-01-12 5:02 ` Patrick McHardy
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=49465C7E.8050103@trash.net \
--to=kaber@trash.net \
--cc=ajax@redhat.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).