From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>
Cc: 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 19:44:42 -0400 [thread overview]
Message-ID: <48A0CEEA.9080104@hp.com> (raw)
In-Reply-To: <20080811.143212.172434871.davem@davemloft.net>
David Miller wrote:
> From: "Parag Warudkar" <parag.warudkar@gmail.com>
> Date: Sun, 10 Aug 2008 21:05:07 -0400
>
>> On Sun, Aug 10, 2008 at 8:30 PM, Brian Haley <brian.haley@hp.com> wrote:
>>
>>> John sent me email off-line saying the patch fixed the problem, but he'd do
>>> more testing over the weekend.
>> I did test the patch and it now spits out "EOF on netlink" like
>> mentioned in bugzilla, which is not consistent with earlier behavior
>> which was to output -
>> unreachable fec0::1 dev lo table unspec proto none src ::1 metric
>> -1 error -101 hoplimit 255 .
>
> We need to resolve this, Brian?
I don't see "EOF on netlink" on 2.6.27-rc2. I can dig-up a 2.6.24
kernel, I'm just wondering if that EOF happens when the IPv6 module
isn't loaded or something?
-Brian
next prev parent reply other threads:[~2008-08-11 23:44 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 [this message]
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=48A0CEEA.9080104@hp.com \
--to=brian.haley@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--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.