Date: Thu, 02 May 1996 19:56:37 +0800 From: Peter Wemm <peter@spinner.DIALix.COM> To: Peter Wemm <peter@freefall.freebsd.org> Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/kern kern_fork.c Message-ID: <199605021156.TAA00890@spinner.DIALix.COM> In-Reply-To: Your message of "Thu, 02 May 1996 04:38:07 MST." <199605021138.EAA18666@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Modified: sys/kern kern_fork.c > This is a minimal change to fix the problem, it will probably be done > better by reordering p_vmspace to be in the startzero section, but it > becomes harder to validate then. Now that I think about it more, this may still not be enough.. If the fork1() is interrupted while inserting the process onto the allproc list, and the VM system walks the severed allproc list during kernel growth, or interrupts a little later when the proc has been inserted but before it's initialised, that would be just as bad. If the kernel traverses the allproc list during an interrupt (eg: network, to allocate more clusters?) to grow the kernel, then all changes to allproc may need to need to be spl protected.. -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605021156.TAA00890>