Messages in this thread | | | Date | Wed, 27 Apr 2011 22:24:20 -0500 | Subject | Re: [PATCH 4/7] seccomp_filter: add process state reporting | From | Will Drewry <> |
| |
On Wed, Apr 27, 2011 at 10:21 PM, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote: >> Adds seccomp and seccomp_filter status reporting to proc. >> /proc/<pid>/status will include a Seccomp field, and >> /proc/<pid>/seccomp_filter will provide read-only access >> to the current filter and bitmask set for seccomp_filters. >> >> Signed-off-by: Will Drewry <wad@chromium.org> >> --- >> fs/proc/array.c | 21 +++++++++++++++++++++ >> fs/proc/base.c | 25 +++++++++++++++++++++++++ >> 2 files changed, 46 insertions(+), 0 deletions(-) > > I'm not againt seccomp_filter. but I dislike to increase /proc/<pid>/status mess. > 1) it's read from a lot of applications, I don't want to worry about performance > thing. 2) 99.99% user never use seccomp. this field is useless for them. > > Can't you make individual seccomp specific file?
Definitely. Would it make sense to have /proc/<pid>/seccomp and /proc/<pid>/seccomp_filter? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |