From owner-svn-src-head@FreeBSD.ORG Wed Dec 12 15:51:25 2012 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 174A19B1; Wed, 12 Dec 2012 15:51:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D55E68FC15; Wed, 12 Dec 2012 15:51:24 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 49CCDB9A9; Wed, 12 Dec 2012 10:51:24 -0500 (EST) From: John Baldwin To: Alfred Perlstein Subject: Re: svn commit: r244105 - in head/sys: kern sys Date: Wed, 12 Dec 2012 10:42:50 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <201212110123.qBB1NpOV060501@svn.freebsd.org> In-Reply-To: <201212110123.qBB1NpOV060501@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201212121042.51362.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 12 Dec 2012 10:51:24 -0500 (EST) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2012 15:51:25 -0000 On Monday, December 10, 2012 8:23:51 pm Alfred Perlstein wrote: > Author: alfred > Date: Tue Dec 11 01:23:50 2012 > New Revision: 244105 > URL: http://svnweb.freebsd.org/changeset/base/244105 > > Log: > Switch the hardwired WITNESS panics to kassert_panic. > > This is an ongoing effort to provide runtime debug information > useful in the field that does not panic existing installations. > > This gives us the flexibility needed when shipping images to a > potentially large audience with WITNESS enabled without worrying > about formerly non-fatal LORs hurting a release. > > Sponsored by: iXsystems Witness doesn't panic on LORs. These are all bigger violations for things like doing sx_sunlock() on a exclusively locked sx lock. That is not safe and is merely going to result in data corruption and other unpleasantness. This sounds like a very bad idea. Did you talk about this anywhere (I have not caught up on various lists yet, so apologies if this has been discussed.) -- John Baldwin