From: Jan Engelhardt <jengelh@xxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
