pidns: Use task_active_pid_ns where appropriate
authorEric W. Biederman <ebiederm@xmission.com>
Tue, 2 Mar 2010 22:51:53 +0000 (14:51 -0800)
committerEric W. Biederman <ebiederm@xmission.com>
Mon, 19 Nov 2012 13:59:09 +0000 (05:59 -0800)
commit17cf22c33e1f1b5e435469c84e43872579497653
treec5cec307c06f7e4ddc26e04e73c8833897b67113
parent49f4d8b93ccf9454284b6f524b96c66d8d7fbccc
pidns: Use task_active_pid_ns where appropriate

The expressions tsk->nsproxy->pid_ns and task_active_pid_ns
aka ns_of_pid(task_pid(tsk)) should have the same number of
cache line misses with the practical difference that
ns_of_pid(task_pid(tsk)) is released later in a processes life.

Furthermore by using task_active_pid_ns it becomes trivial
to write an unshare implementation for the the pid namespace.

So I have used task_active_pid_ns everywhere I can.

In fork since the pid has not yet been attached to the
process I use ns_of_pid, to achieve the same effect.

Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
12 files changed:
arch/powerpc/platforms/cell/spufs/sched.c
arch/um/drivers/mconsole_kern.c
drivers/staging/android/binder.c
fs/hppfs/hppfs.c
fs/proc/root.c
kernel/cgroup.c
kernel/events/core.c
kernel/fork.c
kernel/nsproxy.c
kernel/pid.c
kernel/signal.c
kernel/sysctl_binary.c