netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"YOSHIFUJI Hideaki / _$B5HF#1QL@" <yoshfuji@linux-ipv6.org>,
	"David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: [BUG] can't unload network device's if IPV6 is loaded
Date: Thu, 18 Dec 2003 16:35:50 -0800	[thread overview]
Message-ID: <20031218163550.572cc9b1.shemminger@osdl.org> (raw)
In-Reply-To: <E1AUlxI-00060F-00@gondolin.me.apana.org.au>

On Fri, 12 Dec 2003 22:59:36 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> Stephen Hemminger <shemminger@osdl.org> wrote:
> > In 2.6.0-test11, IPV6 is not correctly cleaning up the network device reference's
> > (ie missing dev_put).  So if I do:
> >        rmmod e100
> > it hangs forever and complains about that not all references have been cleaned up.
> > 
> > This happens even if no IPV6 addresses have been set up. Just having ipv6 available
> > to be loaded at boot up.  The vendor startup scripts (SuSe 9) may be setting something.

Okay, I have a clue about this.. I can reproduce the problem with even
the dummy device.  If the device is removed before the address configuration
timers have completed then it will hang.

Assuming IPV6 is already in the kernel.

Works:
	modprobe dummy; ifconfig dummy0 10.0.0.1; sleep 90; rmmod dummy
Fails:
	modprobe dummy; ifconfig dummy0 10.0.0.1; rmmod dummy

Looks like some tentative entries are floating is space and not in the dst
cache so they don't get destroyed by the notification process.

  reply	other threads:[~2003-12-19  0:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 23:33 [BUG] can't unload network device's if IPV6 is loaded Stephen Hemminger
2003-12-12  0:18 ` David S. Miller
2003-12-12 11:59 ` Herbert Xu
2003-12-19  0:35   ` Stephen Hemminger [this message]
2003-12-15  5:51 ` Dax Kelson
2003-12-16  3:55   ` YOSHIFUJI Hideaki / 吉藤英明
2003-12-16 19:08     ` Stephen Hemminger

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=20031218163550.572cc9b1.shemminger@osdl.org \
    --to=shemminger@osdl.org \
    --cc=davem@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --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).