diff options
| author | Serge E. Hallyn <serue@us.ibm.com> | 2008-05-12 14:02:13 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-13 08:02:24 -0700 |
| commit | 289f8e27ed435dcbefad132def06f4e84351e94f (patch) | |
| tree | e5b3f6206111d5ba1c71eb13a2f01813f4403cee /fs/proc | |
| parent | c8894419acf5e56851de9741c5047bebd78acd1f (diff) | |
| download | kernel_samsung_smdk4412-289f8e27ed435dcbefad132def06f4e84351e94f.zip kernel_samsung_smdk4412-289f8e27ed435dcbefad132def06f4e84351e94f.tar.gz kernel_samsung_smdk4412-289f8e27ed435dcbefad132def06f4e84351e94f.tar.bz2 | |
capabilities: add bounding set to /proc/self/status
There is currently no way to query the bounding set of another task. As there
appears to be no security reason not to, and as Michael Kerrisk points out the
following valid reasons to do so exist:
* consistency (I can see all of the other per-thread/process sets in
/proc/.../status)
* debugging -- I could imagine that it would make the job of debugging an
application that uses capabilities a little simpler.
this patch adds the bounding set to /proc/self/status right after the
effective set.
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Acked-by: Michael Kerrisk <mtk.manpages@gmail.com>
Acked-by: Andrew G. Morgan <morgan@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/proc')
| -rw-r--r-- | fs/proc/array.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/proc/array.c b/fs/proc/array.c index dca997a..9e3b8c3 100644 --- a/fs/proc/array.c +++ b/fs/proc/array.c @@ -298,6 +298,7 @@ static inline void task_cap(struct seq_file *m, struct task_struct *p) render_cap_t(m, "CapInh:\t", &p->cap_inheritable); render_cap_t(m, "CapPrm:\t", &p->cap_permitted); render_cap_t(m, "CapEff:\t", &p->cap_effective); + render_cap_t(m, "CapBnd:\t", &p->cap_bset); } static inline void task_context_switch_counts(struct seq_file *m, |