Messages in this thread | | | Date | Sat, 18 Jun 2011 10:35:59 +0200 | From | Tejun Heo <> | Subject | Re: [PATCH 2/5] ptrace: implement PTRACE_SEIZE |
| |
Hello,
On Sat, Jun 18, 2011 at 09:59:38AM +0200, Denys Vlasenko wrote: > ...unless we plan to introduce PTRACE_O_TRACESTOP (with value 0x00000080) > which enables PTRACE_INTERRUPT and stop notifications independently > of PTRACE_SEIZE. Which would be very useful for e.g. strace.
I know you're a big fan of those option flags but I don't really see the added value in making these behaviors optional rather than keeping things backward compatible - ie. introducing new event needed to be gated somehow so the O flags but SEIZE itself serves as a big gate anyway so I don't see much point in introducing multiple selectable behaviors. It's not like PTRACE_O_TRACESTOP is gonna make anything drastically easier or reduce significant amount of overhead.
Thanks.
-- tejun
| |