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>
Showing
- fs/exec.c 2 additions, 2 deletionsfs/exec.c
- include/linux/sched.h 15 additions, 3 deletionsinclude/linux/sched.h
- kernel/seccomp.c 1 addition, 1 deletionkernel/seccomp.c
- kernel/sys.c 2 additions, 2 deletionskernel/sys.c
- security/apparmor/domain.c 2 additions, 2 deletionssecurity/apparmor/domain.c
Loading
Please register or sign in to comment