From: Eugene Teo <eugeneteo@kernel.sg>
To: David Miller <davem@davemloft.net>
Cc: brian.haley@hp.com, adobriyan@gmail.com, john.gumb@tandberg.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
parag.warudkar@gmail.com
Subject: Re: OOPS, ip -f inet6 route get fec0::1, linux-2.6.26, ip6_route_output, rt6_fill_node+0x175
Date: Tue, 12 Aug 2008 08:41:27 +0800 [thread overview]
Message-ID: <48A0DC37.7080209@kernel.sg> (raw)
In-Reply-To: <48A0D5B4.9050908@kernel.sg>
Eugene Teo wrote:
> David Miller wrote:
>> From: Eugene Teo <eteo@redhat.com>
>> Date: Mon, 11 Aug 2008 16:40:24 +0800
[...]
> With the patch I posted, this is the behaviour I get:
>
> $ ip -f inet6 route get fec0::1
> unreachable fec0::1 dev lo table unspec proto none src
> fe80::214:4fff:fe0f:7332 metric -1 error -101 hoplimit 255
Ok, so there's a mistake in my patch. It should return the loopback MAC
address instead. I'm wondering if the fix should be related to
initialising rt6i_idev in addrconf_init routine like in the upstream
commit: c62dba9011b93fd88fde929848582b2a98309878. The code changed quite
a lot.
Eugene
next prev parent reply other threads:[~2008-08-12 0:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9F6ACAE02B6DD040A1E259977622CFDB033590C3@oslexcp1.eu.tandberg.int>
2008-08-07 20:37 ` OOPS, ip -f inet6 route get fec0::1, linux-2.6.26, ip6_route_output, rt6_fill_node+0x175 Alexey Dobriyan
2008-08-08 4:57 ` Brian Haley
2008-08-11 7:41 ` John Gumb
2008-08-11 8:40 ` Eugene Teo
2008-08-11 20:50 ` David Miller
2008-08-12 0:13 ` Eugene Teo
2008-08-12 0:41 ` Eugene Teo [this message]
2008-08-12 1:40 ` Eugene Teo
2008-08-11 11:03 ` Eugene Teo
2008-08-12 0:41 ` Brian Haley
2008-08-12 9:11 ` OOPS, ip -f inet6 route get fec0::1, linux-2.6.26,ip6_route_output, rt6_fill_node+0x175 John Gumb
2008-08-13 9:01 ` 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=48A0DC37.7080209@kernel.sg \
--to=eugeneteo@kernel.sg \
--cc=adobriyan@gmail.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=john.gumb@tandberg.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parag.warudkar@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).