From: Stefan Beller <stefanbeller@googlemail.com>
To: Oren Laadan <orenl@cellrox.com>,
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>
Subject: Re: [PATCH 2/2] binder: implement namepsace support for Android binder driver
Date: Sun, 22 Dec 2013 11:38:06 +0100 [thread overview]
Message-ID: <52B6C10E.3070002@googlemail.com> (raw)
In-Reply-To: <45c5d62a35f19228a681f5be9834741baabfdb0d.1387706794.git.orenl@cellrox.com>
> #include <linux/uaccess.h>
> #include <linux/vmalloc.h>
> #include <linux/slab.h>
> +#include <linux/ipc_namespace.h>
> #include <linux/pid_namespace.h>
>
> #include "binder.h"
> #include "binder_trace.h"
>
> +/*
> + * Using a private context manager for each binder namespace is sufficient
> + * to isolate between namespaces, because in binder all IPC must be realized
> + * via hanldes obtained from the context manager.
handles
> + *
> + * TODO: currently, most debugfs data is not tracked per binder namespaces.
> + * Except for "procs" which are properly virtualized, everything else is
> + * global, including stats, logs, and dead nodes.
> + */
> +struct binder_namespace {
> + struct kref kref;
> +
> + struct binder_node *context_mgr_node;
> + kuid_t context_mgr_uid;
> + int last_id;
next prev parent reply other threads:[~2013-12-22 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 10:07 [PATCH 0/2] Namespace support for Android binder (under ipc-ns) Oren Laadan
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 [this message]
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=52B6C10E.3070002@googlemail.com \
--to=stefanbeller@googlemail.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=orenl@cellrox.com \
--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
Powered by JetHome