[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m14p77m9uy.fsf@frodo.ebiederm.org>
Date: Thu, 03 Jul 2008 05:27:01 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Daniel Lezcano <dlezcano@...ibm.com>
Cc: Tejun Heo <htejun@...il.com>, Greg Kroah-Hartman <gregkh@...e.de>,
linux-kernel@...r.kernel.org, Al Viro <viro@....linux.org.uk>,
Linux Containers <containers@...ts.osdl.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Benjamin Thery <benjamin.thery@...l.net>
Subject: Re: [PATCH 06/11] sysfs: Implement sysfs tagged directory support.
Daniel Lezcano <dlezcano@...ibm.com> writes:
> The kobject events are sent through a netlink message which is not currently per
> network namespace. Shouldn't be useful to have a way to retrieve from the
> kobject the network namespace or the uevent socket associated with it ? IMHO
> having idr in the kobject + netns pointer associated may help to handle the
> sysfs isolation and makes the uevent per namespace trivial, no ?
Grumble. I have been conveniently been forgetting about that socket.
Similarly we have the user mode helpers to deal with.
For this conversation there is a simple answer. All of that is in the
kobject layer, and works even when you compile sysfs out of your kernel.
Therefore it is a separate problem. And sysfs idr tags have nothing
to do with it.
It is most definitely something we need to come back to. I bet there
are some interesting interactions when you have multiple network devices
with the same name generating events.
Eric
--
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