From: David Miller <davem@davemloft.net>
To: davej@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: ip_rt_bug questions.
Date: Mon, 18 Apr 2011 14:49:09 -0700 (PDT) [thread overview]
Message-ID: <20110418.144909.52209035.davem@davemloft.net> (raw)
In-Reply-To: <20110418214809.GA17443@redhat.com>
From: Dave Jones <davej@redhat.com>
Date: Mon, 18 Apr 2011 17:48:10 -0400
> I managed to trigger this today..
>
> ip_rt_bug: 0.0.0.0 -> 255.255.255.255, ?
>
> if this is useful in some way, maybe it should be enhanced
> to print out something else, like a backtrace ?
>
> Also, should it be a printk_ratelimit() ? Or is there
> ratelimiting done elsewhere in the routing code ?
>
> or should it just be silenced, leaving just the kfree_skb ?
It's a very serious issue, it means we used an input route for
packet output.
Kernel version and what you were doing to trigger this?
next prev parent reply other threads:[~2011-04-18 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 21:48 ip_rt_bug questions Dave Jones
2011-04-18 21:49 ` David Miller [this message]
2011-04-18 21:50 ` David Miller
2011-04-18 21:59 ` Dave Jones
2011-04-19 5:04 ` David Miller
2011-04-19 18:13 ` Dave Jones
2011-04-19 19:22 ` David Miller
2011-05-21 17:16 ` Dave Jones
2011-05-23 1:02 ` David Miller
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=20110418.144909.52209035.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@redhat.com \
--cc=netdev@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).