From: Greg KH <greg@kroah.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Linux Containers <containers@lists.osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Benjamin Thery <benjamin.thery@bull.net>
Subject: Re: [patch 1/1][RFC]Handle uevent per namespace
Date: Mon, 24 Nov 2008 07:31:38 -0800 [thread overview]
Message-ID: <20081124153138.GA16742@kroah.com> (raw)
In-Reply-To: <492A86FA.5080804@fr.ibm.com>
On Mon, Nov 24, 2008 at 11:50:34AM +0100, Daniel Lezcano wrote:
>
> Subject: Handle uevent per namespace
> From: Daniel Lezcano <dlezcano@fr.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
next prev parent reply other threads:[~2008-11-24 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 10:50 [patch 1/1][RFC]Handle uevent per namespace Daniel Lezcano
2008-11-24 15:14 ` Kay Sievers
2008-11-24 15:20 ` Daniel Lezcano
2008-11-24 15:31 ` Greg KH [this message]
2008-11-24 15:55 ` Daniel Lezcano
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=20081124153138.GA16742@kroah.com \
--to=greg@kroah.com \
--cc=benjamin.thery@bull.net \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.