Re: [PATCH 03/10] ptrace: implement PTRACE_SEIZE
From: Pedro Alves
Date: Thu May 19 2011 - 15:38:23 EST
On Thursday 19 May 2011 15:17:28, Tejun Heo wrote:
> But making SEIZE not trigger INTERRUPT and SETOPTIONS without
> requiring TRACED don't seem too difficult. Jan, would that be enough?
> Oleg, what do you think?
UUIC, that opens a race where between SEIZEing and
SETOPTIONS(O_TRACE FORK|VFORK|EXEC...), the tracee can
fork/vfork/clone/exec, without the tracer getting the
nice corresponding PTRACE_EVENT_ events.
In GDBs case, GDB will want to poke at memory
right after attaching, to at least read the
loaded DSO list, so if you can't read tracee
memory without interrupting it, you won't get much
benefit from SEIZE not interrupting.
Not to say other users wouldn't benefit.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/