The patch titled
capabilities: add bounding set to /proc/self/status
has been removed from the -mm tree. Its filename was
capabilities-add-bounding-set-to-proc-self-status.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: capabilities: add bounding set to /proc/self/status
From: "Serge E. Hallyn" <serue@xxxxxxxxxx>
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@xxxxxxxxxx>
Acked-by: Michael Kerrisk <mtk.manpages@xxxxxxxxx>
Acked-by: Andrew G. Morgan <morgan@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/proc/array.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/proc/array.c~capabilities-add-bounding-set-to-proc-self-status fs/proc/array.c
--- a/fs/proc/array.c~capabilities-add-bounding-set-to-proc-self-status
+++ a/fs/proc/array.c
@@ -298,6 +298,7 @@ static inline void task_cap(struct seq_f
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,
_
Patches currently in -mm which might be from serue@xxxxxxxxxx are
origin.patch
git-unionfs.patch
git-vfs-cleanups.patch
reiser4.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
