Re: [PATCH v5 4/6] seccomp: move no_new_privs into seccomp

On Thu, May 22, 2014 at 4:05 PM, Kees Cook wrote: > Since seccomp transitions between threads requires updates to the > no_new_privs flag to be atomic, changes must be atomic. This moves the nnp > flag into the seccomp field as a separate unsigned long for atomic access. > > Signed-off-by: Kees

[PATCH v5 4/6] seccomp: move no_new_privs into seccomp

Since seccomp transitions between threads requires updates to the no_new_privs flag to be atomic, changes must be atomic. This moves the nnp flag into the seccomp field as a separate unsigned long for atomic access. Signed-off-by: Kees Cook --- fs/exec.c |4 ++--

[PATCH v5 4/6] seccomp: move no_new_privs into seccomp

Since seccomp transitions between threads requires updates to the no_new_privs flag to be atomic, changes must be atomic. This moves the nnp flag into the seccomp field as a separate unsigned long for atomic access. Signed-off-by: Kees Cook keesc...@chromium.org --- fs/exec.c |

Re: [PATCH v5 4/6] seccomp: move no_new_privs into seccomp

On Thu, May 22, 2014 at 4:05 PM, Kees Cook keesc...@chromium.org wrote: Since seccomp transitions between threads requires updates to the no_new_privs flag to be atomic, changes must be atomic. This moves the nnp flag into the seccomp field as a separate unsigned long for atomic access.