Messages in this thread | | | Date | Wed, 25 Aug 2004 14:07:33 -0700 | From | Roland McGrath <> | Subject | Re: [PATCH] notify_parent and ptrace cleanup |
| |
> SIGKILL _already_ doesn't actually wake up a ptraced task. It just informs > the tracer, last I looked.
I think it's supposed to do so now, and actually fails to only sometimes in practice and I don't know what the conditions are. But, if you find it acceptable that a traced task stay stopped in trace and not die from SIGKILL until the tracer resumes it or detaches/dies, then aiming for that certainly makes it easier to keep the ptrace code race-free.
> So a new state should be pretty simple, and I really think it would be the > right way to go. That said, I might just be completely wrong - maybe there > are practical problems to that approach that I don't see right now.
I'm going to try it out very soon and then we can see how the testing goes.
Thanks, Roland - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |