[lkml]   [2011]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] man ptrace: add extended description of various ptrace quirks

On Thu, Jul 21, 2011 at 6:51 PM, Oleg Nesterov <> wrote:
> On 07/21, Denys Vlasenko wrote:
>> Deleted several outright false statements:
>> - pid 1 can be traced
>> - tracer is not shown as parent in ps output
>> - PTRACE_ATTACH is not "the same behavior as if tracee had done
>> - SIGSTOP _can_ be injected.
> Yes, this is correct, thanks.
>> +Tracer can not assume that tracee ALWAYS ends its life by reporting
>> +WIFEXITED(status) or WIFSIGNALED(status).
>> +.LP
>> +.\" or can it? Do we include such a promise into ptrace API?
> IIRC, we already discussed this... The traced group leader can
> disappear during mt-exec, otherwise the tracee can never go away
> silently.
>> +Tracer can kill a tracee with ptrace(PTRACE_KILL, pid, 0, 0). This
>> +operation is deprecated, use kill(SIGKILL) or tgkill(SIGKILL) instead.
>> +The problem with this operation is that it requires tracee to be in
>> +signal-delivery-stop, otherwise it may not work (may complete
>> +successfully but won't kill the tracee),
> In short, ptrace(PTRACE_KILL) is more or less ptrace(PTRACE_CONT, SIGKILL),
> but it always returns 0. IOW, it never worked as decribed in the man
> page. And I guess today nobody can explain why PTRACE_KILL exists.
> Oleg.

Does your patch need any revision in the light of Oleg's comments?



Michael Kerrisk
Linux man-pages maintainer;
Author of "The Linux Programming Interface";
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2011-09-21 07:13    [W:0.119 / U:32.636 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site