From owner-freebsd-current@FreeBSD.ORG  Tue Aug 29 20:49:24 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C95D516A542;
	Tue, 29 Aug 2006 20:49:24 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
	[66.23.211.162])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 409FC43D49;
	Tue, 29 Aug 2006 20:49:24 +0000 (GMT) (envelope-from jhb@freebsd.org)
Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7])
	(authenticated bits=0)
	by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k7TKnAKg010001;
	Tue, 29 Aug 2006 16:49:16 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Date: Tue, 29 Aug 2006 16:30:03 -0400
User-Agent: KMail/1.9.1
References: <courier.44EE6A8A.00008655@intron.ac>
	<20060826080410.GA56721@stud.fit.vutbr.cz>
	<courier.44F0083F.0000DC13@intron.ac>
In-Reply-To: <courier.44F0083F.0000DC13@intron.ac>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="gb2312"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608291630.04420.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]);
	Tue, 29 Aug 2006 16:49:17 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.88.3/1761/Tue Aug 29 14:58:36 2006 on
	server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: freebsd-emulation@freebsd.org,
	Intron is my alias on the Internet <mag@intron.ac>
Subject: Re: Linuxulator: Unbreak Mozilla, Firefox and RealPlayer
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Aug 2006 20:49:24 -0000

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