From owner-cvs-all@FreeBSD.ORG Fri Jan 16 15:26:17 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A24C16A4D0; Fri, 16 Jan 2004 15:26:17 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5973043D3F; Fri, 16 Jan 2004 15:26:15 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i0GNOPUd001991; Fri, 16 Jan 2004 18:24:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i0GNOPPE001988; Fri, 16 Jan 2004 18:24:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 16 Jan 2004 18:24:24 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: "Brian F. Feldman" cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_descrip.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 23:26:17 -0000 On Fri, 16 Jan 2004, Dag-Erling Sm=F8rgrav wrote: > "Brian F. Feldman" writes: > > I don't see a reason "newfdp" needs to be locked, since it is not > > referenced by anything yet. If "fdp" alone is locked, that is > > sufficient to ensure they will both be consistent. >=20 > It needs to be locked because it is passed to functions which assert > that it is locked.=20 It sounds like this is an API problem, and is probably what we should fix.= =20 I've found WITNESS an invaluable debugging tool for locking, and when programming on systems without it, it's a very painful experience (i.e., debugging lock orders on Darwin). You've also pointed out that the extra locking work being done is actually unnecessary, so maybe we just need an _unlocked() version of the API, or changes elsewhere?=20 Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research