seccomp.2: Minor tweaks to Mike's patch

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-07-05 10:46:44 +02:00
parent 089761d56d
commit baaf65e88a
1 changed files with 5 additions and 3 deletions

View File

@ -385,13 +385,15 @@ the handler will be ignored in this case and the process always terminates.
.\" See these commits:
.\" seccomp: dump core when using SECCOMP_RET_KILL (b25e67161c295c98acda92123b2dd1e7d8642901)
.\" seccomp: Only dump core when single-threaded (d7276e321ff8a53106a59c85ca46d03e34288893)
Before Linux 4.11, any process terminated this way would not trigger a coredump
Before Linux 4.11,
any process terminated this way would not trigger a coredump
(even though
.B SIGSYS
is documented in
.BR signal (7)
as having a default core action).
Since Linux 4.11, single threaded processes follow standard coredump behavior,
as having a default action of termination with a core dump).
Since Linux 4.11,
single threaded processes follow standard core dump behavior,
but multithreaded processes still do not.
There is no workaround currently for multithreaded processes.
.TP