diff options
author | Eric Paris <eparis@redhat.com> | 2012-01-03 21:25:15 +0400 |
---|---|---|
committer | Eric Paris <eparis@redhat.com> | 2012-01-06 03:52:59 +0400 |
commit | f1c84dae0ecc51aa35c81f19a0ebcd6c0921ddcb (patch) | |
tree | 59d729bb7806e42a13f0ec1657c90b717c314002 /include/linux/capability.h | |
parent | d2a7009f0bb03fa22ad08dd25472efa0568126b9 (diff) | |
download | linux-f1c84dae0ecc51aa35c81f19a0ebcd6c0921ddcb.tar.xz |
capabilities: remove task_ns_* functions
task_ in the front of a function, in the security subsystem anyway, means
to me at least, that we are operating with that task as the subject of the
security decision. In this case what it means is that we are using current as
the subject but we use the task to get the right namespace. Who in the world
would ever realize that's what task_ns_capability means just by the name? This
patch eliminates the task_ns functions entirely and uses the has_ns_capability
function instead. This means we explicitly open code the ns in question in
the caller. I think it makes the caller a LOT more clear what is going on.
Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Serge E. Hallyn <serge.hallyn@canonical.com>
Diffstat (limited to 'include/linux/capability.h')
-rw-r--r-- | include/linux/capability.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/capability.h b/include/linux/capability.h index 63f59fa8769d..e3e8d9cb9b08 100644 --- a/include/linux/capability.h +++ b/include/linux/capability.h @@ -547,7 +547,6 @@ extern bool has_ns_capability_noaudit(struct task_struct *t, struct user_namespace *ns, int cap); extern bool capable(int cap); extern bool ns_capable(struct user_namespace *ns, int cap); -extern bool task_ns_capable(struct task_struct *t, int cap); extern bool nsown_capable(int cap); /* audit system wants to get cap info from files as well */ |