12 Apr
2019
12 Apr
'19
3:25 p.m.
On Thu, Apr 11, 2019 at 04:56:31PM -0700, Kees Cook wrote:
When running without USERNS or PIDNS the seccomp test would hang since it was waiting forever for the child to trigger the user notification since it seems the glibc() abort handler makes a call to getpid(), which would trap again. This changes the getpid filter to getppid, and makes sure ASSERTs execute to stop from spawning the listener.
Reported-by: Shuah Khan shuah@kernel.org Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace") Signed-off-by: Kees Cook keescook@chromium.org
Sorry for the delay, thanks for looking at this!
Reviewed-by: Tycho Andersen tycho@tycho.ws