From: Olaf Kirch <okir@suse.de>
To: netdev@oss.sgi.com
Subject: ip addr flush hangs
Date: Tue, 9 Mar 2004 15:48:24 +0100 [thread overview]
Message-ID: <20040309144824.GD14419@suse.de> (raw)
Hi,
I'm currently debugging the following problem: on a 2.6.3
kernel, when doing this
ifconfig eth0 down
ip addr flush dev eth0
The second command hangs indefinitely. The reason is that the kernel
reports ipv6-all-hosts (ff02::1) when dumping all addresses, but
RTM_DELADDR on ff02::1 doesn't do anything. As /sbin/ip will loop until
the kernel reports no more matching addresses, it will go on like that
forever.
I don't see an obvious fix to this issue. On one hand, calling ifconfig
down will result in a call to addrconf_ifdown(dev, 0). This will clear
the list of unicast addresses assigned to this interface, but will not
clear the list of multicast addresses (it unloads them from the NIC,
and sends IGMP leave packets, but the list of addresses will remain
attached to the device). So it doesn't destroy the interface completely,
it zaps its state just partly, intentionally.
On the other hand, if you manually remove all addresses from the
interface, this will result in a call to addrconf_ifdown(dev, 1),
causing the mcast list to be zapped as well.
This is not entirely consistent. Should a NETDEV_DOWN zap the
ipv6 configuration completely?
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
next reply other threads:[~2004-03-09 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 14:48 Olaf Kirch [this message]
2004-03-09 15:07 ` ip addr flush hangs Olaf Kirch
2004-03-09 19:25 ` David S. Miller
2004-03-09 19:44 ` Andi Kleen
2004-03-09 19:46 ` David S. Miller
2004-03-09 19:47 ` Olaf Kirch
2004-03-09 23:29 ` David S. Miller
2004-03-09 23:56 ` Shirley Ma
2004-03-10 0:06 ` David S. Miller
2004-03-10 3:32 ` YOSHIFUJI Hideaki / 吉藤英明
2004-03-10 7:59 ` Shirley Ma
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=20040309144824.GD14419@suse.de \
--to=okir@suse.de \
--cc=netdev@oss.sgi.com \
/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).