kernel thread as real threads..
PeterJeremy at optushome.com.au
Mon Jan 23 18:01:41 PST 2006
On Mon, 2006-Jan-23 20:38:46 -0500, Daniel Eischen wrote:
>On Tue, 24 Jan 2006, Peter Jeremy wrote:
>> On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote:
>> >POSIX specifies that only 1 thread (the forking thread) is present
>> >after a fork.
>> Just to clarify, I presume you are talking about only one thread
>> existing in the child process and the parent's threads still exist as
>> they did before the fork(). If fork() arbitrarily killed all the
>> threads in the parent process, that would be a real PITA.
>Correct, I assumed we were talking about the child process.
My understanding of Robert's issue was the case where a parent has
multiple threads, one thread does a fork() whilst the remaining
threads are not blocked. If the remaining threads are executing
whilst fork() is copying the process address space, then the child
will could inherit a confused (partially indeterminate) copy of the
parent's address space, depending on what the other threads have
More information about the freebsd-current