From: Oren Laadan <orenl@cellrox.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Linux Containers" <containers@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lxc-devel <lxc-devel@lists.sourceforge.net>,
"Serge Hallyn" <serge@hallyn.com>,
"Eric Biederman" <ebiederm@xmission.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Amir Goldstein" <amir@cellrox.com>,
"Oren Laadan" <orenl@cellrox.com>
Subject: [PATCH 0/2] Namespace support for Android binder (under ipc-ns)
Date: Sun, 22 Dec 2013 05:07:38 -0500 [thread overview]
Message-ID: <cover.1387706794.git.orenl@cellrox.com> (raw)
Hi,
This patch-duo adds namespaces support for the Android binder driver. As
discussed in Plumbers 2013, binder is a form of IPC and therefore will be
tied to ipc namespace.
On the ipc-ns side, the implementation is modelled after generic net-ns
pointers (see commit dec827d), but simplified to suit single user/caller
for now, to reduce complexity.
The binder driver registers with ipc-ns and uses the generic pointer to
store and retrieve its namespace data. That is, each namespace maintains
its own binder context manager - which suffices for separation, since all
transactions require binder handles provided by the context manager.
Thanks,
Oren.
Oren Laadan (2):
ipc namespace: a generic per-ipc pointer and peripc_ops
binder: implement namepsace support for Android binder driver
drivers/staging/android/Kconfig | 1 +
drivers/staging/android/binder.c | 172 ++++++++++++++++++++++++++++++++-------
include/linux/ipc_namespace.h | 29 +++++++
ipc/namespace.c | 9 ++
ipc/util.c | 60 ++++++++++++++
ipc/util.h | 3 +
6 files changed, 244 insertions(+), 30 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-12-22 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 10:07 Oren Laadan [this message]
2013-12-22 10:07 ` [PATCH 1/2] ipc namespace: a generic per-ipc pointer and peripc_ops Oren Laadan
2013-12-22 10:07 ` [PATCH 2/2] binder: implement namepsace support for Android binder driver Oren Laadan
2013-12-22 10:38 ` Stefan Beller
2014-01-08 23:49 ` Greg Kroah-Hartman
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=cover.1387706794.git.orenl@cellrox.com \
--to=orenl@cellrox.com \
--cc=amir@cellrox.com \
--cc=arve@android.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxc-devel@lists.sourceforge.net \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).