Skip to contentSkip to conversation

Uninitialized timer in ip_mc_down

PATCH New Olaf Kirch 1 participant 1 message Mar 25, 2004

Subsystems (2)
lore
Share & tools
lore

Olaf Kirch

author
#0 lore raw

PATCH 1/1 Uninitialized timer in ip_mc_down

Hi,

if you do the following on a downed interface on 2.6, you get two "uninitialized timer" messages from the kernel, along with a stack trace.

	ip addr add 1.2.3.4 dev eth1
	ip addr del 1.2.3.4 dev eth1

The reason is that inetdev_create calls ip_mc_up if and only if the device is up. However, inetdev_destroy calls ip_mc_destroy_dev unconditionally, so that del_timer gets called for the two multicast timers which are uninitialized.

The attached patch seems to fix this. An alternative patch would be to add a check to ip_mc_down to see whether the timers are actually active before deleting them.

Olaf

Signature · 3 lines
Olaf Kirch     |  Stop wasting entropy - start using predictable
[email protected]   |  tempfile names today!
---------------+ 
linux-2.6.4/net/ipv4/devinet.c renamed from linux-2.6.4.orig/net/ipv4/devinet.c +4 -1
@@ -183,7 +183,10 @@
 
 	in_dev->dead = 1;
 
-	ip_mc_destroy_dev(in_dev);
+	/* If the device isn't up, the multicast info isn't
+	 * initialized. */
+	if (in_dev->dev->flags & IFF_UP)
+		ip_mc_destroy_dev(in_dev);
 
 	while ((ifa = in_dev->ifa_list) != NULL) {
 		inet_del_ifa(in_dev, &in_dev->ifa_list, 0);