Messages in this thread | | | Date | Wed, 15 Sep 2004 14:34:19 -0700 | From | Tim Hockin <> | Subject | Re: [patch] kernel sysfs events layer |
| |
On Wed, Sep 15, 2004 at 05:26:29PM -0400, Robert Love wrote: > On Wed, 2004-09-15 at 14:23 -0700, Greg KH wrote: > > > We aren't giving absolute /dev entries here, that's the beauty of the > > kobject tree :) > > Not that I agree, but I don't think it is the absolute /dev entries that > bother him: it is the fact that knowledge of the mount itself is an > information leak. > > Which it is. As root, in my name space, I should rest in the knowledge > that my mounts are secret, I guess. But I just do not see it as a big > problem.
It's a can of worms, is what it is. And I'm not sure what a good fix would be. Would it just be enough to send a generic "mount-table changed" event, and let userspace figure out the rest?
Or really, why is the kernel broadcasting a mount, which originated in userland. Couldn't mount (or a mount wrapper) do that? It's already running in the right namespace... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |