netdev - ipv6: why disable ipv6 on last address removal?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Dec 2009 20:20:46 +0100
From:	Jiri Bohac <jbohac@...e.cz>
To:	netdev@...r.kernel.org
Cc:	Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>
Subject: ipv6: why disable ipv6 on last address removal?

Hi,

I came across a strange behaviour:

When the last IPv6 address of an interface is removed (using e.g.
"ip -6 addr flush ethX"), inet6_addr_del() calls addrconf_ifdown(... , how=1).

This completely removes IPv6 from the interface. (The same thing
is done e.g. on NETDEV_UNREGISTER). An ugly side effect of this
is that it is no longer possible to set the interface IPv6
settings using sysctl. The only way to make the sysctl settings
accessible again seems to be taking the interface down and up.

This is a nightmare for management scripts.

Most other actions, such as NETDEV_DOWN, call
addrconf_ifdown(..., how=0), which keeps the sysctl settings
available.

Is there any reason why inet6_addr_del needs to sets how=1 and
disable IPv6 even more than "ifconfig down" does?

I quickly tested this patch and it did not seem to break
anything:

--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -2185,7 +2185,7 @@ static int inet6_addr_del(struct net *net, int ifindex, struct in6_addr *pfx,
 			   disable IPv6 on this interface.
 			 */
 			if (idev->addr_list == NULL)
-				addrconf_ifdown(idev->dev, 1);
+				addrconf_ifdown(idev->dev, 0);
 			return 0;
 		}
 	}

Thanks,

-- 
Jiri Bohac <jbohac@...e.cz>
SUSE Labs, SUSE CZ

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html