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)
committerJP Abgrall <jpa@google.com>
Tue, 7 Oct 2014 23:42:32 +0000 (16:42 -0700)
commit9d0ff694bc22fb458acb763811a677696c60725b
treec6101621c0fd2e76c8df01893fe91339fa8d6e43
parente985fd474debedb269fba27006eda50d0b6f07ef
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>

Conflicts:
kernel/sys.c
fs/exec.c
include/linux/sched.h
kernel/seccomp.c
kernel/sys.c
security/apparmor/domain.c