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>
Subject: Re: [PATCH] driver core: add uid and gid to devtmpfs
Date: Thu, 11 Apr 2013 09:41:54 -0700 [thread overview]
Message-ID: <87d2u110kt.fsf@xmission.com> (raw)
In-Reply-To: <20130411161936.GA390@kroah.com> (Greg KH's message of "Thu, 11 Apr 2013 09:19:36 -0700")
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
prev parent reply other threads:[~2013-04-11 16:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 16:56 [PATCH] driver core: add uid and gid to devtmpfs Greg KH
2013-04-06 17:09 ` Al Viro
2013-04-06 17:26 ` Greg KH
2013-04-06 17:45 ` Al Viro
2013-04-06 17:58 ` Greg KH
2013-04-07 16:38 ` Kay Sievers
2013-04-08 18:14 ` Rob Landley
2013-04-08 18:25 ` Greg KH
2013-04-09 15:11 ` Rob Landley
2013-04-11 16:08 ` Greg KH
2013-04-10 9:12 ` Ming Lei
2013-04-10 15:56 ` Greg KH
2013-04-10 16:07 ` Ming Lei
2013-04-11 4:10 ` Eric W. Biederman
2013-04-11 15:56 ` Greg KH
2013-04-11 15:57 ` Greg KH
2013-04-11 16:31 ` Eric W. Biederman
2013-04-11 16:43 ` Greg KH
2013-04-11 16:50 ` Eric W. Biederman
2013-04-11 16:19 ` Greg KH
2013-04-11 16:41 ` Eric W. Biederman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2u110kt.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.