lkml.org 
[lkml]   [2011]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH 03/10] ptrace: implement PTRACE_SEIZE
Date
On Thursday 19 May 2011 21:31, Pedro Alves wrote:
> 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.

SEIZE,fork-in-tracee,INTERRUPT sequence is indistinguishable
from SEIZE happening two microseconds later:

fork-in-tracee,SEIZE,INTERRUPT

> In GDBs case, GDB will want to poke at memory
> right after attaching

...where "right after attaching" is defined as "when the first ptrace-stop
is reported". Which will happen very soon.

--
vda


\
 
 \ /
  Last update: 2011-05-20 00:45    [W:0.151 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site