> 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.
yes, now i understand. When using raw clone() then indeed a CLEARTID set
up in X's context does not necesserily have any meaning in Y's (and Z's)
context.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/