From: David Miller <davem@davemloft.net>
To: subramanian.vijay@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [DANGER 8/7]: ipv4: Cache output routes in fib_info nexthops.
Date: Thu, 12 Jul 2012 18:06:32 -0700 (PDT) [thread overview]
Message-ID: <20120712.180632.2257789590224563114.davem@davemloft.net> (raw)
In-Reply-To: <CAGK4HS_-fQYnmcbBwEE=JywzAO7_nnE8QAOCXk3-WQOjCimPiA@mail.gmail.com>
From: Vijay Subramanian <subramanian.vijay@gmail.com>
Date: Thu, 12 Jul 2012 17:52:54 -0700
> ip_rcv_finish() eventually calls ip_route_input_slow() wherein
> fib_lookup() initially returns a res.type of RTN_UNICAST (why not
> RTN_LOCAL?).
Strange, since only this specific patch causes the problem there must
be some issue with the size of struct fib_info or something like that
triggering the problem. Something might be corrupted in the nexthops.
I wonder if there is some uninitialized data somewhere, or something
silly like that.
next prev parent reply other threads:[~2012-07-13 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 17:47 [DANGER 8/7]: ipv4: Cache output routes in fib_info nexthops David Miller
2012-07-13 0:52 ` Vijay Subramanian
2012-07-13 1:06 ` David Miller [this message]
2012-07-13 11:10 ` David Miller
2012-07-13 20:03 ` Vijay Subramanian
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=20120712.180632.2257789590224563114.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=subramanian.vijay@gmail.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).