From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: davem@davemloft.net
Cc: herbert@gondor.apana.org.au,
mirko.parthey@informatik.tu-chemnitz.de,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
shemminger@osdl.org, yoshfuji@linux-ipv6.org
Subject: Re: PROBLEM: 2.6.11-rc2 hangs on bridge shutdown (br0)
Date: Sun, 06 Feb 2005 14:31:07 +0900 (JST) [thread overview]
Message-ID: <20050206.143107.39728239.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20050205210411.7e18b8e6.davem@davemloft.net>
In article <20050205210411.7e18b8e6.davem@davemloft.net> (at Sat, 5 Feb 2005 21:04:11 -0800), "David S. Miller" <davem@davemloft.net> says:
> On Sun, 06 Feb 2005 13:37:23 +0900 (JST)
> YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[(B <yoshfuji@linux-ipv6.org> wrote:
>
> > How about making dst->ops->dev_check() like this:
> >
> > static int inline dst_dev_check(struct dst_entry *dst, struct net_device *dev)
> > {
> > if (dst->ops->dev_check)
> > return dst->ops->dev_check(dst, dev)
> > else
> > return dst->dev == dev;
> > }
>
> Oh I see. That would work, and it seems the simplest, and
> lowest risk fix for this problem.
Well...
Here, lo is going down.
rt->rt6i_dev = lo and rt->rt6i_idev = ethX.
I think we already see dst->dev == dev (==lo) now.
So, I doubt that fix the problem.
The source of problem is entry (*) which still on routing entry,
not on gc list. And, the owner of entry is not routing table but
unicast/anycast address structure(s).
We need to "kill" active address on the other interfaces.
*: rt->rt6i_dev = lo and rt->rt6i_idev = ethX
BTW, I wish we could shut down eth0 during lo is pending...
--yoshfuji
next prev parent reply other threads:[~2005-02-06 5:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 16:22 Mirko Parthey
2005-01-31 17:40 ` Matthias-Christian Ott
2005-02-01 17:36 ` Mirko Parthey
2005-02-02 16:08 ` Matthias-Christian Ott
2005-02-05 12:48 ` Matthias-Christian Ott
2005-02-05 5:24 ` Herbert Xu
2005-02-05 5:38 ` David S. Miller
2005-02-05 6:11 ` Herbert Xu
2005-02-05 6:13 ` David S. Miller
2005-02-05 6:46 ` Herbert Xu
2005-02-05 10:45 ` Herbert Xu
2005-02-06 11:41 ` Herbert Xu
2005-02-06 12:30 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-06 21:01 ` Herbert Xu
2005-02-05 10:50 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-05 18:32 ` Herbert Xu
2005-02-06 4:02 ` David S. Miller
2005-02-06 5:01 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-06 4:10 ` David S. Miller
2005-02-06 4:37 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-06 5:04 ` David S. Miller
2005-02-06 5:31 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2005-02-06 5:50 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-06 7:00 ` Herbert Xu
2005-02-06 6:53 ` Herbert Xu
2005-02-06 6:52 ` Herbert Xu
2005-02-06 6:51 ` Herbert Xu
2005-02-08 1:29 ` [IPSEC] Move dst->child loop from dst_ifdown to xfrm_dst_ifdown Herbert Xu
2005-02-08 1:31 ` Herbert Xu
2005-02-15 22:53 ` David S. Miller
2005-02-05 11:14 ` PROBLEM: 2.6.11-rc2 hangs on bridge shutdown (br0) Andre Tomt
2005-02-05 11:39 ` YOSHIFUJI Hideaki / 吉藤英明
[not found] ` <4204B27F.5040202@tomt.net>
2005-02-05 11:55 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-05 18:33 ` Herbert Xu
2005-02-06 10:55 ` Andre Tomt
2005-02-06 11:28 ` YOSHIFUJI Hideaki / 吉藤英明
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=20050206.143107.39728239.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mirko.parthey@informatik.tu-chemnitz.de \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®