From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay@vrfy.org>,
        Ming Lei <ming.lei@canonical.com>
References: <20130406165600.GA29660@kroah.com> <87y5cpvhaz.fsf@xmission.com>
	<20130411161936.GA390@kroah.com>
Date: Thu, 11 Apr 2013 09:41:54 -0700
In-Reply-To: <20130411161936.GA390@kroah.com> (Greg KH's message of "Thu, 11
	Apr 2013 09:19:36 -0700")
Message-ID: <87d2u110kt.fsf@xmission.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [PATCH] driver core: add uid and gid to devtmpfs
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1046
Lines: 27

Greg KH <gregkh@linuxfoundation.org> 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 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/