From owner-freebsd-arch@FreeBSD.ORG  Thu Nov 15 20:51:14 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id C80914AD;
 Thu, 15 Nov 2012 20:51:14 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 63A6F8FC19;
 Thu, 15 Nov 2012 20:51:13 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA06347;
 Thu, 15 Nov 2012 22:51:11 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1TZ6P0-000Nza-LF; Thu, 15 Nov 2012 22:51:10 +0200
Message-ID: <50A555BD.1010105@FreeBSD.org>
Date: Thu, 15 Nov 2012 22:51:09 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:16.0) Gecko/20121030 Thunderbird/16.0.2
MIME-Version: 1.0
To: Adrian Chadd <adrian@FreeBSD.org>
Subject: Re: [RFQ] make witness panic an option
References: <CAJ-Vmo=i=Amo_QqHi4GnGie0Gc0YnK3XaRKjvBO-=SFboFYPmA@mail.gmail.com>
 <1353001175.1217.153.camel@revolution.hippie.lan>
 <CAJ-FndBP5Pi=SCpyBLK3b=HM_gQ9u8M4+1tLk9tA5X-gqismVA@mail.gmail.com>
 <1353009310.1217.172.camel@revolution.hippie.lan>
 <CAJ-Vmo=S3a1pyLHOe+SayVNDe=mAogQnkNpnSTakpOm56EdOUQ@mail.gmail.com>
In-Reply-To: <CAJ-Vmo=S3a1pyLHOe+SayVNDe=mAogQnkNpnSTakpOm56EdOUQ@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: attilio@FreeBSD.org, Ian Lepore <freebsd@damnhippie.dyndns.org>,
 freebsd-arch@FreeBSD.org, freebsd-hackers@FreeBSD.org
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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, 15 Nov 2012 20:51:14 -0000

on 15/11/2012 22:00 Adrian Chadd said the following:
> But I think my change is invaluable for development, where you want to
> improve and debug the locking and lock interactions of a subsystem.

My practical experience was that if you mess up one lock in one place, then it
is a total mess further on.  but apparently you've got a different practical
experience :-)

What would indeed be invaluable to _me_ - if the LOR messages also produced the
stack(s) where a supposedly correct lock order was learned.

-- 
Andriy Gapon