[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202106301606.E710FF81EC@keescook>
Date: Wed, 30 Jun 2021 16:06:56 -0700
From: Kees Cook <keescook@...omium.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Michael Kerrisk <mtk.manpages@...il.com>,
linux-api@...r.kernel.org, Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>, linux-man@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] seccomp.2: Clarify that bad system calls kill the thread
On Wed, Jun 30, 2021 at 03:11:23PM -0500, Eric W. Biederman wrote:
>
> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com>
> ---
> man2/seccomp.2 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/man2/seccomp.2 b/man2/seccomp.2
> index a3421871f0f4..bde54c3e3e99 100644
> --- a/man2/seccomp.2
> +++ b/man2/seccomp.2
> @@ -69,9 +69,10 @@ The only system calls that the calling thread is permitted to make are
> .BR exit_group (2)),
> and
> .BR sigreturn (2).
> -Other system calls result in the delivery of a
> +Other system calls result in the termination of the calling thread,
> +or termination of the entire process with the
> .BR SIGKILL
> -signal.
> +signal when there is only one thread.
> Strict secure computing mode is useful for number-crunching
> applications that may need to execute untrusted byte code, perhaps
> obtained by reading from a pipe or socket.
Thanks!
Acked-by: Kees Cook <keescook@...omium.org>
--
Kees Cook
Powered by blists - more mailing lists