Greg KH <[email protected]> writes: > On Wed, Apr 10, 2013 at 09:10:12PM -0700, Eric W. Biederman wrote: >> Still it approaches being twisted to have files like >> /sys/class/net/eth0/uevent that anyone can read that will only return >> values in the initial user namespace. > > Side note, I don't think that ethernet network devices have uids :)
I didn't think any devices had uids... :) The generic uevent file was the first place I could think of where we output this information to userspace. And I don't think that uevent file is specific network devices. There isn't anything that limits our netlink messages to clients in the initial user namespace either. Nothing huge, but there are some goofy kernel/user interaction cases that show up when you add this functionality. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
