mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay@vrfy.org>,
	Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH] driver core: add uid and gid to devtmpfs
Date: Thu, 11 Apr 2013 09:08:25 -0700	[thread overview]
Message-ID: <20130411160825.GA24536@kroah.com> (raw)
In-Reply-To: <1365520315.18069.56@driftwood>

On Tue, Apr 09, 2013 at 10:11:55AM -0500, Rob Landley wrote:
> 
> Or do you think it will simply never cause a problem, so there's no
> need to worry?

Based on the limited number of drivers that will be using this
interface, I don't think there's any need to worry.  But I will be glad
to revisit this in the future if needed.

> >> Or is this because containers allow UID/GID to be redefined, and
> >> thus imposing magic values on userspace can now be mapped away or
> >> something?
> >
> >I don't understand, what do you mean by this?
> 
> I mean that each container can have its own UID/GID namespace now, I
> was wondering if a driver claims a UID that an existing root
> filsystem is already using for something else, can a container remap
> it away so it doesn't conflict? Or will it still need manual udev
> rules to adjust at hotplug time?

I don't know how containers deal with the userspace major/minor device
nodes today at all, so I can't answer that.  But see the review comments
from Eric that he sent, I'll make the needed changes based on that so
all should be ok after that.

thanks,

greg k-h

  reply	other threads:[~2013-04-11 16:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 16:56 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 [this message]
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

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=20130411160825.GA24536@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=viro@ZenIV.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome