From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org
Subject: Re: ipv6 neighbour code keeps interfaces held
Date: Thu, 11 Sep 2008 14:46:19 -0700 (PDT) [thread overview]
Message-ID: <20080911.144619.17474001.davem@davemloft.net> (raw)
In-Reply-To: <1221149559.6986.30.camel@johannes.berg>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu, 11 Sep 2008 18:12:38 +0200
> On Wed, 2008-09-10 at 16:40 -0700, David Miller wrote:
>
> > Here is a quick patch that might resolve this specific situation.
> > Let me know how it works for you:
>
> I haven't seen it again so far, but it's not necessarily an indication
> that it worked. But normally I think I probably would have seen it
> already by now.
Thanks for the feedback.
I put this fix into net-next-2.6, and what I'll likely do is backport
this to net-2.6 and -stable if you still don't see if after a few more
days.
prev parent reply other threads:[~2008-09-11 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 21:18 ipv6 neighbour code keeps interfaces held Johannes Berg
2008-09-10 23:40 ` David Miller
2008-09-10 23:57 ` Johannes Berg
2008-09-11 0:00 ` David Miller
2008-09-11 7:11 ` Rami Rosen
2008-09-11 16:12 ` Johannes Berg
2008-09-11 21:46 ` David Miller [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=20080911.144619.17474001.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
/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