net sched: printk message severity
The previous patch encourage me to go look at all the messages in the network scheduler and fix them. Many messages were missing any severity level. Some serious ones that should never happen were turned into WARN(), and the random noise messages that were handled changed to pr_debug(). Signed-off-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
00c60a8312
commit
6ff9c3644e
@@ -527,7 +527,8 @@ pop_stack:
|
||||
|
||||
stack_overflow:
|
||||
if (net_ratelimit())
|
||||
printk("Local stack overflow, increase NET_EMATCH_STACK\n");
|
||||
printk(KERN_WARNING "tc ematch: local stack overflow,"
|
||||
" increase NET_EMATCH_STACK\n");
|
||||
return -1;
|
||||
}
|
||||
EXPORT_SYMBOL(__tcf_em_tree_match);
|
||||
|
Reference in New Issue
Block a user