Searched hist:"225778 d68d98e7cfe2579f8d8b2d7b76f8541b8b" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/kernel/ |
| H A D | pid_namespace.c | diff 225778d68d98e7cfe2579f8d8b2d7b76f8541b8b Thu Aug 02 10:35:35 CDT 2012 Eric W. Biederman <ebiederm@xmission.com> pidns: Deny strange cases when creating pid namespaces.
task_active_pid_ns(current) != current->ns_proxy->pid_ns will
soon be allowed to support unshare and setns.
The definition of creating a child pid namespace when
task_active_pid_ns(current) != current->ns_proxy->pid_ns could be that
we create a child pid namespace of current->ns_proxy->pid_ns. However
that leads to strange cases like trying to have a single process be
init in multiple pid namespaces, which is racy and hard to think
about.
The definition of creating a child pid namespace when
task_active_pid_ns(current) != current->ns_proxy->pid_ns could be that
we create a child pid namespace of task_active_pid_ns(current). While
that seems less racy it does not provide any utility.
Therefore define the semantics of creating a child pid namespace when
task_active_pid_ns(current) != current->ns_proxy->pid_ns to be that the
pid namespace creation fails. That is easy to implement and easy
to think about.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|