On Wed, 31 Oct 2012 13:09:27 -0700 Kees Cook <keesc...@chromium.org> wrote:
> Adds the seccomp mode to the /proc/$pid/status file so the state of > seccomp can be externally examined. There's no reason here for anyone to apply this patch to anything. Presumably you see some value to our users - please share your thoughts with us ;) > --- a/fs/proc/array.c > +++ b/fs/proc/array.c > @@ -327,6 +327,13 @@ static inline void task_cap(struct seq_file *m, struct > task_struct *p) > render_cap_t(m, "CapBnd:\t", &cap_bset); > } > > +static inline void task_seccomp(struct seq_file *m, struct task_struct *p) > +{ > +#ifdef CONFIG_SECCOMP hm, OK, cpuset_task_status_allowed() is a no-op if CONFIG_CPUSETS=n, so there is precedent for fields vanishing with Kconfig changes. > + seq_printf(m, "Seccomp:\t%d\n", p->seccomp.mode); Get thee yon unto Documentation/filesystems/proc.txt! > +#endif > +} -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/