sched: move no_new_privs into new atomic flags
authorKees Cook <keescook@chromium.org>
Wed, 21 May 2014 22:23:46 +0000 (15:23 -0700)
committerKees Cook <keescook@chromium.org>
Fri, 18 Jul 2014 19:13:38 +0000 (12:13 -0700)
Since seccomp transitions between threads requires updates to the
no_new_privs flag to be atomic, the flag must be part of an atomic flag
set. This moves the nnp flag into a separate task field, and introduces
accessors.

Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Reviewed-by: Andy Lutomirski <luto@amacapital.net>

No differences found