From: Julien BLACHE <jb@jblache.org>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] fib6_del() bug from 2.6.34-rc1 still present in 2.6.34
Date: Mon, 24 May 2010 11:54:20 +0200 [thread overview]
Message-ID: <878w7962wj.fsf@sonic.technologeek.org> (raw)
In-Reply-To: <4BF9DCB7.8040308@cn.fujitsu.com> (Shan Wei's message of "Mon, 24 May 2010 09:56:07 +0800")
Shan Wei <shanwei@cn.fujitsu.com> wrote:
Hi,
> I saw the warning on 2.6.34-rc3. But on net-next tree the warning disappeared.
> So I think the bug is fixed in net-next tree. My NIC driver is r8169.
>
> The net-next tree is newer than 2.6.34, maybe the fix is not queued to 2.6.34.
> So the warning also be present in 2.6.34.
> Can you try net-next tree firstly?
Unfortunately, this tree has a number of issues that prevent a
successful boot into userland on my machine :/
Any idea what the fix(es) is so I can test it out?
JB.
--
Julien BLACHE <http://www.jblache.org>
<jb@jblache.org> GPG KeyID 0xF5D65169
prev parent reply other threads:[~2010-05-24 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 15:55 [regression] fib6_del() bug from 2.6.34-rc1 still present in 2.6.34 Julien BLACHE
2010-05-24 1:56 ` Shan Wei
2010-05-24 9:54 ` Julien BLACHE [this message]
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=878w7962wj.fsf@sonic.technologeek.org \
--to=jb@jblache.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shanwei@cn.fujitsu.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