]> git.karo-electronics.de Git - karo-tx-linux.git/commit
proc: don't show nonexistent capabilities
authorAndrew Vagin <avagin@openvz.org>
Thu, 25 Oct 2012 01:15:16 +0000 (12:15 +1100)
committerStephen Rothwell <sfr@canb.auug.org.au>
Fri, 2 Nov 2012 05:01:01 +0000 (16:01 +1100)
commit07532b173d500ec9fccd0880c4f7f2a87bb35019
tree049bf64a000dafb2cd214b4f48ac915563a7cd93
parent8180adaef7f6e28b72b1f32c54ab5cbc2ee964dc
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>
fs/proc/array.c