From owner-freebsd-arch@FreeBSD.ORG  Thu Apr  8 14:40:08 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8D62E16A4CF; Thu,  8 Apr 2004 14:40:08 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CB7D643D66; Thu,  8 Apr 2004 14:40:07 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i38Le7NG029213;
	Thu, 8 Apr 2004 23:40:07 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Pawel Jakub Dawidek <pjd@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 08 Apr 2004 23:36:47 +0200."
             <20040408213647.GL661@darkness.comp.waw.pl> 
Date: Thu, 08 Apr 2004 23:40:07 +0200
Message-ID: <29212.1081460407@critter.freebsd.dk>
cc: freebsd-arch@freebsd.org
Subject: Re: mtx_lock_recurse/mtx_unlock_recurse functions
	(proof-of-concept). 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2004 21:40:08 -0000

In message <20040408213647.GL661@darkness.comp.waw.pl>, Pawel Jakub Dawidek wri
tes:
>
>--0+35XlDF45POFHfm
>Content-Type: text/plain; charset=iso-8859-2
>Content-Disposition: inline
>Content-Transfer-Encoding: quoted-printable
>
>Hi.
>
>As was discussed, it will be helpful to have functions, that are able
>to acquire lock recursively, even if lock itself isn't recursable.

Sounds evil to me...

Does your patch also make witness aware of this ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.