Date: Tue, 18 Dec 2001 18:53:17 -0600 From: Alfred Perlstein <bright@mu.org> To: John Baldwin <jhb@FreeBSD.org> Cc: current@freebsd.org, Julian Elischer <julian@elischer.org> Subject: Re: Is this a bug in the fork() code? Message-ID: <20011218185317.O59831@elvis.mu.org> In-Reply-To: <XFMail.011218164043.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Tue, Dec 18, 2001 at 04:40:43PM -0800 References: <XFMail.011218163100.jhb@FreeBSD.org> <XFMail.011218164043.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* John Baldwin <jhb@FreeBSD.org> [011218 18:41] wrote:
>
> Actually, it's a bit worse than that. The parent process will sleep on itself
> waiting to be woken up, but when the child exits, it will wake up init
> (p->p_pptr) not the waiting process, so if you do a rfork(..., RFNOWAIT |
> RFPPWAIT); then the parent process will hang and never return.
>
> Perhaps fork1() should return EINVAL if both flags are set.
>
Good idea.
--
-Alfred Perlstein [alfred@freebsd.org]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011218185317.O59831>