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:13:40 +0800 [thread overview]
Message-ID: <48A0D5B4.9050908@kernel.sg> (raw)
In-Reply-To: <20080811.135003.105171324.davem@davemloft.net>
David Miller wrote:
> From: Eugene Teo <eteo@redhat.com>
> Date: Mon, 11 Aug 2008 16:40:24 +0800
>
>> Brian Haley wrote:
>>> Alexey Dobriyan wrote:
>>>> On Thu, Aug 07, 2008 at 07:00:56PM +0200, John Gumb wrote:
>>>>> Scenario: no ipv6 default route set.
>>>>> # ip -f inet6 route get fec0::1
>>>>>
>>>>> BUG: unable to handle kernel NULL pointer dereference at 00000000
>>>>> IP: [<c0369b85>] rt6_fill_node+0x175/0x3b0
>>>>> EIP is at rt6_fill_node+0x175/0x3b0
>>>> 0xffffffff80424dd3 is in rt6_fill_node (net/ipv6/route.c:2191).
>>>> 2186 } else
>>>> 2187 #endif
>>>> 2188 NLA_PUT_U32(skb, RTA_IIF, iif);
>>>> 2189 } else if (dst) {
>>>> 2190 struct in6_addr saddr_buf;
>>>> 2191 ====> if
>>>> (ipv6_dev_get_saddr(ip6_dst_idev(&rt->u.dst)->dev,
>>>> ^^^^^^^^^^^^^^^^^^^^^^^^
>>>> NULL
>>>>
>>>> 2192 dst, 0, &saddr_buf) == 0)
>>>> 2193 NLA_PUT(skb, RTA_PREFSRC, 16,
>>>> &saddr_buf);
>>>> 2194 }
>>> The commit that changed this can't be reverted easily, but the patch
>>> below works for me.
>>>
>>> Fix NULL de-reference in rt6_fill_node() when there's no IPv6 input
>>> device present in the dst entry.
>>>
>>> Signed-off-by: Brian Haley <brian.haley@hp.com>
>> Cc: Stable <stable@kernel.org>
>
> We've already determined from one tester that the behavior is
> changing with Brian's patch. Furthermore I haven't applied it
> to mainline so it isn't anywhere near being submittable for
> -stable.
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
John emailed me that he will be testing this patch. I have not tested
Brian's patch.
> I submit all relevant networking bug fixes to -stable when they are
> ready and in a proper state to be submitted, you don't have to do it
> for me. Sending me a gentle reminder or nudge, on the other hand, is
> fine.
Thanks for letting me know. I wasn't familiar, but I welcome the hint.
Thanks,
Eugene
next prev parent reply other threads:[~2008-08-12 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 17:00 OOPS, ip -f inet6 route get fec0::1, linux-2.6.26, ip6_route_output, rt6_fill_node+0x175 John Gumb
2008-08-07 20:37 ` 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 [this message]
2008-08-12 0:41 ` Eugene Teo
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=48A0D5B4.9050908@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.