On Fri, 16 Aug 2002, Ingo Molnar wrote:
>
> On Thu, 15 Aug 2002, Linus Torvalds wrote:
>
> > process X
> >
> > fork()
> > -------> Process Y
> > clone()
> > ----> thread Z
> >
> > exit()
> > THIS MUST NOT
> > WRITE TO MEMORY
> > IN Z!!
>
> i guess i'm just being difficult, but process (thread) Y and thread Z
> share the same VM, right? So it's a threaded application, and as such i'd
> expect it to free its state when exiting.
You're being dense.
The problem spot is the _fork_ from process X. Which gives a address in
process' _X_ virtual address space - used for SETTID.
See? Process _X_ is not threaded, and is not maintaining any thread data
structures.
Linus
-
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/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:41 EST