Date: Tue, 29 Aug 2006 16:30:03 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: freebsd-emulation@freebsd.org, Intron is my alias on the Internet <mag@intron.ac> Subject: Re: Linuxulator: Unbreak Mozilla, Firefox and RealPlayer Message-ID: <200608291630.04420.jhb@freebsd.org> In-Reply-To: <courier.44F0083F.0000DC13@intron.ac> References: <courier.44EE6A8A.00008655@intron.ac> <20060826080410.GA56721@stud.fit.vutbr.cz> <courier.44F0083F.0000DC13@intron.ac>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 26 August 2006 04:37, Intron is my alias on the Internet wrote: > This problem has confused me for a long time. > > The lock allproc_lock is more conservative than either p2->p_mtx or > proctree_lock. It is the real protector of process tree. Not quite. allproc_lock protects allproc and zombproc and p_list inside of each process. proctree_lock protects the parent-child relationships as as process group and session pointers and lists. allproc_lock also protects a few global variables related to PID allocation. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200608291630.04420.jhb>