From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: [PATCH 06/11] sysfs: Implement sysfs tagged directory support. Date: Thu, 03 Jul 2008 05:27:01 -0700 Message-ID: References: <20080618170729.808539948@theryb.frec.bull.fr> <20080618170731.002784342@theryb.frec.bull.fr> <485F04E1.70204@gmail.com> <486706C9.9040303@gmail.com> <4869D314.5030403@gmail.com> <486A0751.9080602@gmail.com> <486AF4FA.8020805@gmail.com> <486B060C.7030607@gmail.com> <486C4515.1070007@gmail.com> <486CB051.5000507@fr.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <486CB051.5000507-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org> (Daniel Lezcano's message of "Thu, 03 Jul 2008 12:56:17 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Daniel Lezcano Cc: Tejun Heo , Greg Kroah-Hartman , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Al Viro , Linux Containers , Andrew Morton , Benjamin Thery List-Id: containers.vger.kernel.org Daniel Lezcano 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