[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081124153138.GA16742@kroah.com>
Date: Mon, 24 Nov 2008 07:31:38 -0800
From: Greg KH <greg@...ah.com>
To: Daniel Lezcano <dlezcano@...ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Netdev List <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Linux Containers <containers@...ts.osdl.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Benjamin Thery <benjamin.thery@...l.net>
Subject: Re: [patch 1/1][RFC]Handle uevent per namespace
On Mon, Nov 24, 2008 at 11:50:34AM +0100, Daniel Lezcano wrote:
>
> Subject: Handle uevent per namespace
> From: Daniel Lezcano <dlezcano@...ibm.com>
>
> At present when a network device is destroyed, inside a network
> namespace, and this device has the same name as one network device
> belonging to the initial network namespace (eg. eth0), the udev daemon
> will disable the interface in the initial network namespace.
>
> IMHO, udev should not receive this event. The uevents should be per
> namespace or at least do not send events when not for the initial
> network namespace.
IMHO, network namespaces are a mess and not something that you should be
doing at all :)
> The following patch is a RFC for making uevent namespace aware. I don't
> know this part of the kernel code, so I am pretty sure t is not the
> right way to do that :)
Like Kay said, please don't change the kobject core for this, try just
filtering in the network core the events that you handle there.
good luck,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists