diff options
| author |   Eric W. Biederman <ebiederm@xmission.com> | 2012-08-02 08:35:35 -0700 |
|---|---|---|
| committer | Eric W. Biederman <ebiederm@xmission.com> | 2012-11-19 05:59:13 -0800 |
| commit | 225778d68d98e7cfe2579f8d8b2d7b76f8541b8b (patch) | |
| tree | d4bc4b78c3e19821eaaffacc5341d02328bcd3c9 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | pidns: Wait in zap_pid_ns_processes until pid_ns->nr_hashed == 1 (diff) | |
| download | linux-dev-225778d68d98e7cfe2579f8d8b2d7b76f8541b8b.tar.xz linux-dev-225778d68d98e7cfe2579f8d8b2d7b76f8541b8b.zip | |
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions