| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 03 Jul 2008 13:08:52 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Tejun Heo <htejun@...il.com> Cc: Daniel Lezcano <dlezcano@...ibm.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. Tejun Heo <htejun@...il.com> writes: > Related delta: I've been thinking that uevents should be part of sysfs > not kobject as that's what the userland is gonna associate the event > with. Would that solve the problem you're thinking about? The good news is that uevent_sock is currently restricted to just the initial network namespace (so the functionality completely disappears in the other namespaces), and that it is broadcast only. So it should be possible to look at who the client is and by some magic criterian decide if it should receive the broadcast message. The call to the user mode helper is trickier. How do we setup the proper user space context. None of this is fundamentally hard just different work, for a different day. 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