public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: "'Kay Sievers'" <kay@vrfy.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] driver: core: add security labels to devtmpfs
Date: Fri, 5 Jun 2015 20:50:45 +0900	[thread overview]
Message-ID: <20150605115045.GC12012@kroah.com> (raw)
In-Reply-To: <016401d09f80$fdb0b130$f9121390$@samsung.com>

On Fri, Jun 05, 2015 at 08:15:55PM +0900, Namjae Jeon wrote:
> > On Fri, Jun 05, 2015 at 07:10:23PM +0900, Namjae Jeon wrote:
> > > Add support for setting security labels(e.g. smack or selinux labels) to
> > > devtmpfs device nodes. In this manner, drivers can specify desired security
> > > label in their device_type->devnode or class->devnode method.
> > 
> > What driver wants to do this?  And how does it determine the proper
> > security label from within the kernel?  Isn't that something that only
> > userspace can know/set properly?
> Yes, It is possible by userspace, But This api change will help to set uid/gid
> and xattr values easily without need of complex userspace scripts in absence of
> udev like helper.

If you want to do things like this, use a "complex" userspace script
like Android has for their startup (hint, it's just a tiny bash script,
nothing "complex" about it at all...)

> And security label that decided as per each embedded system will be set by
> this api in driver.

Exactly how will that happen?  I don't see any users of it.

greg k-h

      reply	other threads:[~2015-06-05 11:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 10:10 [PATCH 2/3] driver: core: add security labels to devtmpfs Namjae Jeon
2015-06-05 10:20 ` 'Greg Kroah-Hartman'
2015-06-05 11:15   ` Namjae Jeon
2015-06-05 11:50     ` 'Greg Kroah-Hartman' [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=20150605115045.GC12012@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox