From owner-freebsd-current Sat Nov 24 17: 7:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id 724BE37B416 for ; Sat, 24 Nov 2001 17:07:24 -0800 (PST) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id fAP17Nn01358; Sun, 25 Nov 2001 02:07:23 +0100 (CET) (envelope-from mux) Date: Sun, 25 Nov 2001 02:07:23 +0100 From: Maxime Henrion To: current@FreeBSD.org Cc: Hiten Pandya Subject: Re: some info (new) Message-ID: <20011125020723.C831@nebula.noos.fr> References: <20011125015325.B831@nebula.noos.fr> <20011125005921.45291.qmail@web21104.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011125005921.45291.qmail@web21104.mail.yahoo.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > MH> The lock order verification is not part of the mtx > MH> API. It's debugging > MH> stuff activated by default in -CURRENT. If you do > MH> not want to see these > MH> warnings, remove ``options WITNESS'' from your > MH> kernel conf or patch the > MH> code to solve the problem :-) > > hi, > i know that bit.. the WITNESS option is commented > which says about the mutexes, but what i mean.. if i > wanted to patch a lock order reversal... how would i > do that... (i am newbie [not so newbie..]).. First, locate the faulting part of code, then just modify it so that it enforces the established lock order. The way to fix it is somewhat obvious, but it may indeed be very hard in some cases. Good luck, Maxime Henrion -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message