Re: [PATCH] pidfd: Stop taking cred_guard_mutex
From: Kees Cook <hidden>
Date: 2020-03-11 18:49:59
Also in:
linux-api, linux-fsdevel, linux-mm, lkml, stable
Possibly related (same subject, not in this thread)
- 2020-03-11 · Re: [PATCH] pidfd: Stop taking cred_guard_mutex · Jann Horn <jannh@google.com>
- 2020-03-11 · Re: [PATCH] pidfd: Stop taking cred_guard_mutex · Bernd Edlinger <hidden>
- 2020-03-10 · Re: [PATCH] pidfd: Stop taking cred_guard_mutex · Bernd Edlinger <hidden>
- 2020-03-10 · Re: [PATCH] pidfd: Stop taking cred_guard_mutex · Jann Horn <jannh@google.com>
- 2020-03-10 · Re: [PATCH] pidfd: Stop taking cred_guard_mutex · Jann Horn <jannh@google.com>
On Tue, Mar 10, 2020 at 03:57:35PM -0500, Eric W. Biederman wrote:
So ptrace_attach and seccomp use the cred_guard_mutex to guarantee a deadlock.
Well, that's the result, but seccomp uses it because it wants to be certain that credentials and no_new_privs are changed together "atomically". -- Kees Cook