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)
commit1d4457f99928a968767f6405b4a1f50845aa15fd
tree522641b08f4a465035910a74a3871ad38e62df01
parent8855d608c145c1ca0e26f4da00741080bb49d80d
sched: move no_new_privs into new atomic flags

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>
fs/exec.c
include/linux/sched.h
kernel/seccomp.c
kernel/sys.c
security/apparmor/domain.c