On Sun, Dec 22, 2013 at 05:07:40AM -0500, Oren Laadan wrote:
> Add namespaces support for the Android binder driver.
> As binder is an IPC mechanism, tie its namespace to IPC_NS.
Why does binder need namespace support?
Does the Android userspace code support this?
I need an ack from the Android
On Sun, Dec 22, 2013 at 05:07:40AM -0500, Oren Laadan wrote:
Add namespaces support for the Android binder driver.
As binder is an IPC mechanism, tie its namespace to IPC_NS.
Why does binder need namespace support?
Does the Android userspace code support this?
I need an ack from the Android
> #include
> #include
> #include
> +#include
> #include
>
> #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
> + *
Add namespaces support for the Android binder driver.
As binder is an IPC mechanism, tie its namespace to IPC_NS.
In binder, the first process to call BINDER_SET_CONTEXT_MGR ioctl
becomes the manager with context 0, and thereafter IPC is realized
through binder handles obtained from this manager.
Add namespaces support for the Android binder driver.
As binder is an IPC mechanism, tie its namespace to IPC_NS.
In binder, the first process to call BINDER_SET_CONTEXT_MGR ioctl
becomes the manager with context 0, and thereafter IPC is realized
through binder handles obtained from this manager.
#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
6 matches
Mail list logo
