Re: kern/49017: vfork does not suspend all threads

[Martin Husemann <martin%duskware.de@localhost>]

The following reply was made to PR kern/49017; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: Christos Zoulas <christos%zoulas.com@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/49017: vfork does not suspend all threads
Date: Thu, 6 Apr 2017 11:03:09 +0200

 On Wed, Apr 05, 2017 at 04:26:04PM -0400, Christos Zoulas wrote:
 > On Apr 5,  7:20pm, martin%duskware.de@localhost (Martin Husemann) wrote:
 > -- Subject: Re: kern/49017: vfork does not suspend all threads
 > 
 > |  Using vfork() in a program with multiple active threads is madness,
 > |  posix_spawn() is the only sensible way.
 > 
 > Why is that? We allow it, so it should do something reasonable/useful...
 > Or we should not allow it...
 
 We now have two processes with active threads each and a shared vmpspace.
 This sounds like completely out of spec for the unix process model to me
 and I'd call it madness.
 
 Martin