summaryrefslogtreecommitdiff
path: root/fs/proc_namespace.c
diff options
context:
space:
mode:
authorAndrew Vagin <avagin@openvz.org>2012-12-18 00:03:10 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2012-12-18 01:15:22 (GMT)
commit7b9a7ec565505699f503b4fcf61500dceb36e744 (patch)
tree1a0c3f91d613e4e07e858ba93e28344056356c7c /fs/proc_namespace.c
parent992fb6e170639b0849bace8e49bf31bd37c4123c (diff)
downloadlinux-fsl-qoriq-7b9a7ec565505699f503b4fcf61500dceb36e744.tar.xz
proc: don't show nonexistent capabilities
Without this patch it is really hard to interpret a bounding set, if CAP_LAST_CAP is unknown for a current kernel. Non-existant capabilities can not be deleted from a bounding set with help of prctl. E.g.: Here are two examples without/with this patch. CapBnd: ffffffe0fdecffff CapBnd: 00000000fdecffff I suggest to hide non-existent capabilities. Here is two reasons. * It's logically and easier for using. * It helps to checkpoint-restore capabilities of tasks, because tasks can be restored on another kernel, where CAP_LAST_CAP is bigger. Signed-off-by: Andrew Vagin <avagin@openvz.org> Cc: Andrew G. Morgan <morgan@kernel.org> Reviewed-by: Serge E. Hallyn <serge.hallyn@canonical.com> Cc: Pavel Emelyanov <xemul@parallels.com> Reviewed-by: Kees Cook <keescook@chromium.org> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: James Morris <jmorris@namei.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/proc_namespace.c')
0 files changed, 0 insertions, 0 deletions