From: Roland Dreier <roland@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH/RFC] ipv6: fib: Drop cached routes with dead neighbours on fib GC
Date: Fri, 11 Jan 2013 13:10:20 -0800 [thread overview]
Message-ID: <CAL1RGDXG=7vnf2xReeN6jR0MwSGhqcep4cN5FUApcUTJpt_mCg@mail.gmail.com> (raw)
In-Reply-To: <20130111140119.GC8436@order.stressinduktion.org>
On Fri, Jan 11, 2013 at 6:01 AM, Hannes Frederic Sowa
<hannes@stressinduktion.org> wrote:
> The report I meant was actually not referred in this bug report:
> http://article.gmane.org/gmane.linux.network/224832
>
> ENETDOWN was also observed via bridges.
Yes, I would have to think any report of ENETDOWN with ipv6 and
bridging is quite likely to be the same issue I hit.
- R.
prev parent reply other threads:[~2013-01-11 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:44 [PATCH/RFC] ipv6: fib: Drop cached routes with dead neighbours on fib GC Roland Dreier
2013-01-10 22:18 ` David Miller
2013-01-11 8:57 ` David Laight
2013-01-11 21:13 ` Roland Dreier
2013-01-11 23:50 ` David Miller
2013-01-11 13:40 ` Hannes Frederic Sowa
2013-01-11 14:01 ` Hannes Frederic Sowa
2013-01-11 21:10 ` Roland Dreier [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='CAL1RGDXG=7vnf2xReeN6jR0MwSGhqcep4cN5FUApcUTJpt_mCg@mail.gmail.com' \
--to=roland@kernel.org \
--cc=davem@davemloft.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;
as well as URLs for NNTP newsgroup(s).