lkml.org 
[lkml]   [2009]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [PATCH 1/1] ptrace: do_notify_parent_cldstop: fix the wrong ->nsproxy usage
    Date
    > While this change is correct in any case (I hope), I wonder whether
    > we need another one:
    [...]
    > If the sub-thread is not traced, but ->group_leader is, perhaps it makes
    > more sense to notify the leader's tracer, not parent?

    I don't think so.

    > Not that I think this is really important. Just curious about what was
    > the intent.

    Here is how I would describe the intent (admittedly this logic is
    retrospective, not necessarily articulated as such when the code was
    written). If the the triggering task is ptrace'd, this report is "for
    ptrace purposes"--even if it's the CLD_STOPPED case. Otherwise, what's
    being reported is "the whole POSIX process is now stopped as per POSIX
    definitions". The latter properly goes to the parent of the process,
    which is the group_leader->real_parent.


    Thanks,
    Roland


    \
     
     \ /
      Last update: 2009-05-27 03:09    [W:4.468 / U:1.184 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site