[lkml]   [2011]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 1/4] signal: fix SIGCONT notification code
    On Wed, 22 Dec 2010 12:13:15 +0100, Tejun Heo wrote:
    > If SIGCONT is received while the child process is stopped, the code should
    > be CLD_CONTINUED. If SIGCONT is recieved while the child process is in the
    > process of being stopped, it should be CLD_STOPPED.

    If a process does
    kill (PID, SIGSTOP);
    <varying delay, possibly even from a different process>
    kill (PID, SIGCONT);

    does it mean the PID's parent may get different waitid() results?
    Or even that PID will finally remain still `T (stopped)'?

    I do not see it has any userland impact, the
    PTRACE_ATTACH-to-T(stopped)-process is already racy for different reasons.


     \ /
      Last update: 2011-01-12 21:51    [W:0.018 / U:10.992 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site