mirror of https://github.com/mkerrisk/man-pages
prctl.2, seccomp.2: Clarify that SECCOMP_SET_MODE_STRICT disallows exit_group(2)
These days, glibc implements _exit() as a wrapper around exit_group(2). (When seccomp was originally introduced, this was not the case.) Give the reader a clue that, despite what glibc is doing, what SECCOMP_SET_MODE_STRICT permits is the true _exit(2) system call, and not exit_group(2). Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
7a79bb301a
commit
85fbef7408
|
@ -431,7 +431,9 @@ set to
|
|||
the only system calls that the thread is permitted to make are
|
||||
.BR read (2),
|
||||
.BR write (2),
|
||||
.BR _exit (2),
|
||||
.BR _exit (2)
|
||||
(but not
|
||||
.BR exit_group (2)),
|
||||
and
|
||||
.BR sigreturn (2).
|
||||
Other system calls result in the delivery of a
|
||||
|
|
|
@ -54,7 +54,9 @@ values:
|
|||
The only system calls that the calling thread is permitted to make are
|
||||
.BR read (2),
|
||||
.BR write (2),
|
||||
.BR _exit (2),
|
||||
.BR _exit (2)
|
||||
(but not
|
||||
.BR exit_group (2)),
|
||||
and
|
||||
.BR sigreturn (2).
|
||||
Other system calls result in the delivery of a
|
||||
|
|
Loading…
Reference in New Issue