From: Laura Abbott <labbott@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Benjamin Gaignard" <benjamin.gaignard@linaro.org>,
"Sandeep Patil" <sspatil@google.com>,
driverdevel <devel@driverdev.osuosl.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Riley Andrews" <riandrews@android.com>,
linux-api@vger.kernel.org,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>
Subject: Re: [PATCH v5 2/2] staging: ion: create one device entry per heap
Date: Mon, 16 Oct 2017 15:09:11 -0700 [thread overview]
Message-ID: <2a9246e0-eafa-7812-6cf4-2482ff1ed158@redhat.com> (raw)
In-Reply-To: <20171010091151.rfdsphstboubm7ps@sirena.co.uk>
On 10/10/2017 02:11 AM, Mark Brown wrote:
> On Mon, Oct 09, 2017 at 05:10:37PM -0700, Laura Abbott wrote:
>> On 10/09/2017 03:08 PM, Mark Brown wrote:
>>> On Mon, Oct 09, 2017 at 02:25:47PM -0700, Laura Abbott wrote:
>
>>>> Anyway, to move this forward I think we need to see a proof of concept
>>>> of using selinux to protect access to specific heaps.
>
>>> Aren't Unix permissions enough with separate files or am I
>>> misunderstanding what you're looking to see a proof of concept for?
>
>> The goal is to be able to restrict heap access to certain services
>> and selinux groups on Android so straight unix permissions aren't
>> sufficient.
>
> Oh, there's Android users for this? The users I was aware of were
> non-Android. Though even so I'd have thought that given that SELinux is
> a superset of Unix file permissions it ought to be sufficient to be able
> to use them. I'd been thinking people were suggesting SELinux as a
> replacement for file permissions, using the single file and the greater
> capabilities of SELinux.
>
Unix file permissions are necessary but not sufficient, they
can be used separately. Mostly what I want to see before
merging this is an example that splitting the Ion heaps provides
more protection than just keeping /dev/ion.
Thanks,
Laura
next prev parent reply other threads:[~2017-10-16 22:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 13:20 [PATCH v5 0/2] staging: ion: get one device " Benjamin Gaignard
2017-09-27 13:20 ` [PATCH v5 1/2] staging: ion: simplify ioctl args checking function Benjamin Gaignard
2017-10-09 9:21 ` Benjamin Gaignard
2017-10-09 16:45 ` Laura Abbott
2017-09-27 13:20 ` [PATCH v5 2/2] staging: ion: create one device entry per heap Benjamin Gaignard
2017-10-02 18:07 ` Laura Abbott
2017-10-03 16:48 ` Mark Brown
2017-10-03 21:42 ` Laura Abbott
2017-10-03 23:08 ` Sandeep Patil
2017-10-03 23:37 ` Laura Abbott
2017-10-04 10:17 ` Mark Brown
2017-10-05 13:06 ` Benjamin Gaignard
2017-10-09 21:25 ` Laura Abbott
2017-10-09 22:08 ` Mark Brown
2017-10-10 0:10 ` Laura Abbott
2017-10-10 9:11 ` Mark Brown
2017-10-16 22:09 ` Laura Abbott [this message]
2017-10-17 12:39 ` Benjamin Gaignard
2017-10-18 20:07 ` Laura Abbott
2017-10-23 15:19 ` Benjamin Gaignard
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=2a9246e0-eafa-7812-6cf4-2482ff1ed158@redhat.com \
--to=labbott@redhat.com \
--cc=arve@android.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=sspatil@google.com \
--cc=sumit.semwal@linaro.org \
/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
all inboxes | Powered by JetHome®