From: David Miller <davem@davemloft.net>
To: eugeneteo@kernel.sg
Cc: brian.haley@hp.com, parag.warudkar@gmail.com,
akpm@linux-foundation.org, bugme-daemon@bugzilla.kernel.org,
netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 11297] New: OOPS in rt6_fill_node
Date: Mon, 11 Aug 2008 18:40:26 -0700 (PDT) [thread overview]
Message-ID: <20080811.184026.02436525.davem@davemloft.net> (raw)
In-Reply-To: <28fa9c5e0808111828w2a9f1133y75c785f70b683ff2@mail.gmail.com>
From: "Eugene Teo" <eugeneteo@kernel.sg>
Date: Tue, 12 Aug 2008 09:28:05 +0800
> On Tue, Aug 12, 2008 at 9:10 AM, Eugene Teo <eugeneteo@kernel.sg> wrote:
> > On Tue, Aug 12, 2008 at 8:41 AM, Brian Haley <brian.haley@hp.com> wrote:
> >> Parag Warudkar wrote:
> >>>
> >>> What output do you see with your patch?
> >>
> >> # ip -f inet6 route get fec0::1
> >> unreachable fec0::1 dev lo table unspec proto none src
> >> 2001:1890:1109:a10:218:feff:fe7f:49c8 metric -1 error -101 hoplimit 255
> >
> > Hmm, I tried it on an older kernel that doesn't have Yoshfuji-san's
> > ipv6_get_saddr() changes,
> > and it should display the output with the loopback MAC address instead
> > of ethX MAC address.
> > Correct me if I am wrong.
>
> Evidence of me still sleepy. Not the MAC address but the ipv6 address...
Hmmm... from what I understand so far based upon Parag's most
recent reply, Brian's patch should be OK.
Does everyone else agree?
next prev parent reply other threads:[~2008-08-12 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11297-10286@http.bugzilla.kernel.org/>
2008-08-10 4:31 ` [Bugme-new] [Bug 11297] New: OOPS in rt6_fill_node Andrew Morton
2008-08-10 14:03 ` Parag Warudkar
2008-08-11 0:30 ` Brian Haley
2008-08-11 1:05 ` Parag Warudkar
2008-08-11 21:32 ` David Miller
2008-08-11 23:44 ` Brian Haley
2008-08-12 0:01 ` Parag Warudkar
2008-08-12 0:41 ` Brian Haley
2008-08-12 1:06 ` Parag Warudkar
2008-08-12 1:10 ` Eugene Teo
2008-08-12 1:28 ` Eugene Teo
2008-08-12 1:40 ` David Miller [this message]
2008-08-12 2:06 ` Brian Haley
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=20080811.184026.02436525.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=brian.haley@hp.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=eugeneteo@kernel.sg \
--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).