[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081107.225529.45534653.davem@davemloft.net>
Date: Fri, 07 Nov 2008 22:55:29 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: ebiederm@...ssion.com
Cc: dlezcano@...ibm.com, containers@...ts.osdl.org, den@...nvz.org,
xemul@...nvz.org, netdev@...r.kernel.org
Subject: Re: [PATCH 2/2] net: Guaranetee the proper ordering of the
loopback device. v2
From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Thu, 06 Nov 2008 07:36:00 -0800
> I was recently hunting a bug that occurred in network namespace
> cleanup. In looking at the code it became apparrent that we have
> and will continue to have cases where if we have anything going
> on in a network namespace there will be assumptions that the
> loopback device is present. Things like sending igmp unsubscribe
> messages when we bring down network devices invokes the routing
> code which assumes that at least the loopback driver is present.
>
> Therefore to avoid magic initcall ordering hackery that is hard
> to follow and hard to get right insert a call to register the
> loopback device directly from net_dev_init(). This guarantes
> that the loopback device is the first device registered and
> the last network device to go away.
>
> But do it carefully so we register the loopback device after
> we clear dev_boot_phase.
>
> Signed-off-by: Eric W. Biederman <ebiederm@...well.aristanetworks.com>
Applied.
--
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
Powered by blists - more mailing lists