seccomp.2: Explicitly note that other threads survive SECCOMP_RET_KILL_THREAD

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/seccomp.2 b/man2/seccomp.2
index 88b47f645d485defce1bce79d9700dd7ad508b2c..2e912940eddd243554dbb2f093d64e3e7278b43e 100644 (file)
--- a/man2/seccomp.2
+++ b/man2/seccomp.2
@@ -400,14 +400,15 @@ In decreasing order of precedence,
 the values that may be returned by a seccomp filter are:
 .TP
 .BR SECCOMP_RET_KILL_THREAD " (or " SECCOMP_RET_KILL )
-This value results in the thread exiting immediately
-without executing the system call.
+This value results in immediate termination of the thread
+that made the system call.
+The system call is not executed.
+Other threads in the same thread group will continue to execute.
+.IP
 The thread terminates as though killed by a
 .B SIGSYS
-signal
-.RI ( not
-.BR SIGKILL ).
-Even if a signal handler has been registered and otherwise catches
+signal.
+Even if a signal handler has been registered for
 .BR SIGSYS ,
 the handler will be ignored in this case and the thread always terminates.
 .IP