netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: netdev@oss.sgi.com
Subject: Re: unregister_netdevice: waiting for tun6to4 to become free.
Date: Thu, 16 Dec 2004 02:32:17 +0200	[thread overview]
Message-ID: <20041216003217.GA6058@ee.oulu.fi> (raw)
In-Reply-To: <20040923.172253.125681726.yoshfuji@linux-ipv6.org>

On Thu, Sep 23, 2004 at 05:22:53PM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> > > If I boot with net.ipv6.conf.default.forward = 1 in sysctl.conf - but 
> > > then after the boot do echo 1 > /proc/sys/net/ipv6/conf/all/forward (to 
> > > actually get it running)
> > > I have the ipv6/conf/default/forwarding set in sysctl.conf on all the 
> > > routers, and it seems zebra sets the ipv6/conf/all/forwarding later on.
> > if default is set first, then tunnels created, followed by setting 
> > "all"; everything breaks down on ifdown.
> > 
> > pretty neat :)
> 
> Thank you everyone for tracking down this bug.
> I will fix this bug and come up with patch tomorrow (or so).
> Thanks again.
Hiya

There seems to be a regression, I've recently bumped into this bug again.
(2.6.9-fc3-latest-thing, I didn't see anything relevant in latest Linus bk).
It did work for some time ago, since them my ipv6 configuration has changed
and I've updated the kernel quite a bit.

   if [ "$device" != "sit0" ]; then
                if ipv6_exec_ip tunnel show $device 2>/dev/null | LC_ALL=C grep -q -w "ipv6/ip"; then
                        ipv6_exec_ip tunnel del $device

is what triggers it, tunnel del gets stuck with a refcnt of 1, device is no
longer in /proc/net/dev. Tunnel is run on top of PPPoE and it's a dynamic
sixxs.net aiccu thing. IPv6 forwarding is on.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282023 seems to be related
too.

      parent reply	other threads:[~2004-12-16  0:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 21:24 unregister_netdevice: waiting for tun6to4 to become free Pekka Pietikainen
2004-09-21  0:59 ` Jeff Garzik
2004-09-21  6:24   ` Andre Tomt
2004-09-22 12:08     ` David Woodhouse
2004-09-22 18:15       ` David S. Miller
2004-09-23  6:18         ` YOSHIFUJI Hideaki / 吉藤英明
     [not found]     ` <20040921121332.GR31616@rei.reeler.org>
     [not found]       ` <4151E680.80203@tomt.net>
     [not found]         ` <20040922211942.GA1674@postel.suug.ch>
     [not found]           ` <41523670.1090603@tomt.net>
     [not found]             ` <41523EC5.20805@tomt.net>
2004-09-23  7:13               ` Andre Tomt
2004-09-23  8:07                 ` Andre Tomt
2004-09-23  8:22                   ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-24 19:05                     ` [PATCH/RFC] PATCH: IPV6: Fix multiple leakages (is Re: unregister_netdevice: waiting for tun6to4 to become free.) YOSHIFUJI Hideaki / 吉藤英明
2004-09-24 20:51                       ` Andre Tomt
2004-09-27 19:23                       ` David S. Miller
2004-12-16  0:32                     ` Pekka Pietikainen [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=20041216003217.GA6058@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.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).