[lkml]   [2002]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] user-vm-unlock-2.5.31-A2

On Thu, 15 Aug 2002, Linus Torvalds wrote:
> See? Process _X_ is not threaded, and is not maintaining any thread data
> structures.

.. Just to clarify: CLONE_SETTID is useful even outside of threading, so X
wants to use CLONE_SETTID simply because it keeps track of it's children
that way - but it is otherwise completely traditional, and depends on
SIGCHLD to tell it when the children have died.

The child (Y) it forks off, however, may use thread (Z) for some subtask.
Not pthreads, it might be just a clone-by-hand. So it may be doing an
exit while it's address space is still actively used by another thread -
but just because (X) wanted to use CLONE_SETTID to get the child
information on (Y) does _not_ mean that it's address space (and thus
that of Z) would somehow be updated at its exit.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.115 / U:2.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site