> Well, ptrace_report_syscall() checks current->exit_code after > ptrace_notify() and does send_sig(). But yes, PTRACE_SETSIGINFO is > doesn't work.
Oh, right. Aside from PTRACE_SETSIGINFO, it's more subtly wrong in that it generates a new signal (to be seen again by ptrace) rather than delivering it. > Also. If PT_TRACESYSGOOD is set ptrace_report_syscall() adds 0x80 > which is then reported by wait(&status), this doesn't look right. Right. > OK, I assume otherwise you acked these changes, I am going to update > the changelog and send them to akpm with your acked-by included. Yes. Thanks, Roland
