From: David Miller <davem@davemloft.net>
To: jengelh@medozas.de
Cc: kaber@trash.net, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/2] nefilter: use pr_devel instead of pr_debug
Date: Thu, 22 Apr 2010 04:00:26 -0700 (PDT) [thread overview]
Message-ID: <20100422.040026.102028104.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1004221248010.31972@obet.zrqbmnf.qr>
From: Jan Engelhardt <jengelh@medozas.de>
Date: Thu, 22 Apr 2010 12:53:38 +0200 (CEST)
> On Thursday 2010-04-22 12:46, Patrick McHardy wrote:
> Once upon a time, most of the Netfilter debug statements read like:
>
> #ifdef TURNMEON
> #define duprintf(...) printk(...)
> #else
> #define duprintf(...)
> #endif
>
> So the intention was to have a behavior that requires a developer to
> explicitly turn on debugging in source code. By adding a line like
> #define IP_DEBUG_FIREWALL at the start. (I explicitly exclude
> blocks like #ifdef CONFIG_ in this consideration.)
>
> When pr_debug became available, parts of the netfilter code moved to
> pr_debug, as that behaved just the same - the only change was that the
> variable was now named DEBUG across the entire kernel source rather than
> IP_DEBUG_FIREWALL - whatever the actual name was.
Jan, things are even better now. With dynamic debug enabled you can
select down to the source file and line which debug printk you want
enabled.
No functionality has been removed, in fact you have more control
over the situation now, not less.
Eventually it will probably be even more efficient by using dynamic
code patching as well.
next prev parent reply other threads:[~2010-04-22 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 13:21 nf-next: two small ones Jan Engelhardt
2010-04-21 13:21 ` [PATCH 1/2] nefilter: use pr_devel instead of pr_debug Jan Engelhardt
2010-04-22 10:46 ` Patrick McHardy
2010-04-22 10:53 ` Jan Engelhardt
2010-04-22 11:00 ` Patrick McHardy
2010-04-22 11:01 ` David Miller
2010-04-22 11:04 ` Patrick McHardy
2010-04-22 11:00 ` David Miller [this message]
2010-04-22 10:55 ` David Miller
2010-04-21 13:21 ` [PATCH 2/2] netfilter: rectify XT_FUNCTION_MAXNAMELEN usage Jan Engelhardt
2010-04-22 10:48 ` Patrick McHardy
2010-04-26 12:47 ` Jan Engelhardt
2010-04-27 13:35 ` 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=20100422.040026.102028104.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--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).