From: Brian Haley <brian.haley@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: parag.warudkar@gmail.com, bugme-daemon@bugzilla.kernel.org,
netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 11297] New: OOPS in rt6_fill_node
Date: Sun, 10 Aug 2008 20:30:31 -0400 [thread overview]
Message-ID: <489F8827.4030904@hp.com> (raw)
In-Reply-To: <20080809213101.0927a808.akpm@linux-foundation.org>
Andrew Morton wrote:
> Can you please confirm the version numbers here? 2.6.26-rc4 was OK,
> but 2.6.26 and 2.6.27-rc2 are busted?
This commit would have broken this, which git-whatchanged shows as being
in 2.6.24-rc4:
commit 5e5f3f0f801321078c897a5de0b4b4304f234da0
Author: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Mon Mar 3 21:44:34 2008 +0900
[IPV6] ADDRCONF: Convert ipv6_get_saddr() to ipv6_dev_get_saddr().
Since most users of ipv6_get_saddr() pass non-NULL as
dst argument, use ipv6_dev_get_saddr() directly.
Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Most people have default IPv6 routes, which is probably why it hasn't
been seen.
> Brian had a patch but apparently things still aren't right (see the
> full bugzilla report for details).
John sent me email off-line saying the patch fixed the problem, but he'd
do more testing over the weekend.
-Brian
next prev parent reply other threads:[~2008-08-11 0:31 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 [this message]
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
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=489F8827.4030904@hp.com \
--to=brian.haley@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.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.