From: "Thomas P." <tom@huno.net>
To: netdev@oss.sgi.com
Cc: hadi@cyberus.ca
Subject: CONFIG_NET_CLS_ACT massive debug output
Date: Sun, 29 Aug 2004 00:49:38 +0200 [thread overview]
Message-ID: <145338506.20040829004938@huno.net> (raw)
hi,
i'm getting a lot of the following messages:
Aug 28 23:31:32 knecht kernel: ing_filter: fixed ppp0 out ppp0
Aug 28 23:32:02 knecht last message repeated 4 times
Aug 28 23:32:32 knecht last message repeated 78 times
Now i found the following:
+ if (NULL == skb->input_dev) {
+ skb->input_dev = skb->dev;
+ printk("ing_filter: fixed %s out %s\n",skb->input_dev->name,skb->dev->name);
+ }
and i guess i could just comment it out, but the message is probably there
for a reason. So is there anything wrong? The rule that causes this is:
tc qdisc add dev ppp0 handle ffff: ingress
tc filter add dev ppp0 parent ffff: protocol ip prio 50 u32 match ip src \
0.0.0.0/0 police rate 1416kbit burst 10k drop flowid :1
Thanks for your help!
Thomas
reply other threads:[~2004-08-28 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=145338506.20040829004938@huno.net \
--to=tom@huno.net \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
/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).