Re: [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race

From: Luming Yu
Date: Fri May 23 2008 - 01:24:56 EST

> This is the key thing that makes no sense to me. What do you mean by
> "deliver" here? The normal meaning of to "deliver" a signal means that
> get_signal_to_deliver() dequeues and processes it. This can never happen
> inside any other kernel code path. It certainly can never happen inside
> ptrace_stop or ptrace_notify.

"deliver" here I mean get_signal_to_deliver()...
Please clarify, in ptrace_notify code path, is it allowed that ptraced
thread can ignore signals (such as SIGTRAP) without telling debugger
what happened? This is key problem I'm not quite sure... Because if
the test doesn't block SIGTRAP, it works on IA64 too.. Hope I have
made the problem clear...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at