The description in the man page is confusing; it makes it sound like setting the PTRACE_O_EXITKILL flag on any tracee makes it so that all tracees are killed if the tracer exits. The description from the commit that introduced PTRACE_O_EXITKILL offers a different explanation: "If the tracer exits it sends SIGKILL to every tracee which has this bit set". Cc: Oleg Nesterov <oleg@xxxxxxxxxx> Signed-off-by: Omar Sandoval <osandov@xxxxxxxxxxx> --- man2/ptrace.2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man2/ptrace.2 b/man2/ptrace.2 index 4f1e7d865..96dfc0003 100644 --- a/man2/ptrace.2 +++ b/man2/ptrace.2 @@ -464,9 +464,9 @@ which are specified by the following flags: .TP .BR PTRACE_O_EXITKILL " (since Linux 3.8)" .\" commit 992fb6e170639b0849bace8e49bf31bd37c4123 -If a tracer sets this flag, a +Send a .B SIGKILL -signal will be sent to every tracee if the tracer exits. +signal to the tracee if the tracer exits. This option is useful for ptrace jailers that want to ensure that tracees can never escape the tracer's control. .TP -- 2.11.0 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
