From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 12:42:19 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78F30180; Sun, 25 Nov 2012 12:42:19 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5BEBF8FC0C; Sun, 25 Nov 2012 12:42:17 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7225582lbb.13 for ; Sun, 25 Nov 2012 04:42:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/ZgxWTcmy7bW4zmJmA9hpWjmPo8HwffJiEFY4Zl3HMw=; b=dWCkF44fYD/BMhGodD7WygNvt0/CKcOSuZipXG8UTj6sZmAyX9m3GdpvTbw9fop/wZ lkaSUUOE0O5gLbm4QLv5URLMAgFSfIlJPfXf4Vog0oT4v4OrmFbNSRgydG0iZmK6SwQG WtoPu7gcI4gW+0/z+AaQNgjj+Ix0iFzumN3Xyu6IdNJQ0cFaSG6B9OLeltYLuw1DSyoN AH0DlxZny3WuCU59W/xI5Ml7hUD76hOdp7aGpvAV68scK6yuCNaPFMg6PhAtFn++Qa5f phXfLa7Czu6QxuT1Jud6SUe8vs0CejWKI8hj+jXyK8owH9tByfVGjwpQ1OtNtWApYX+4 uEVA== MIME-Version: 1.0 Received: by 10.112.28.98 with SMTP id a2mr3800413lbh.110.1353847337007; Sun, 25 Nov 2012 04:42:17 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 04:42:16 -0800 (PST) In-Reply-To: <20121125123920.GI1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 12:42:16 +0000 X-Google-Sender-Auth: A_uJPsdkWDmbZj44H85r7_DJHmg Message-ID: Subject: Re: [RFQ] make witness panic an option From: Attilio Rao To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 12:42:19 -0000 On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: > On Thu, Nov 15, 2012 at 04:39:55PM +0000, Attilio Rao wrote: >> On 11/15/12, Adrian Chadd wrote: >> > On 15 November 2012 05:27, Giovanni Trematerra >> > wrote: >> > >> >> I really do think that is a very bad idea. >> >> When a locking assertion fails you have just to stop your mind and >> >> think what's wrong, >> >> no way to postpone on this. >> > >> > Not all witness panics are actually fatal. For a developer who is >> > sufficiently cluey in their area, they are quite likely able to just >> > stare at the code paths for a while to figure out why the >> > incorrectness occured. >> >> The problem is that such mechanism can be abused, just like the >> BLESSING one and that's why this is disabled by default. > > WITNESS is a development tool. We don't ship production kernels with > WITNESS even compiled in. What is more efficient use of developer time: > going through full reboot cycle every time or reading the warning from > console, unloading a module, fixing the bug and loading it again? > > And if this option is turned off by default what is the problem? Yes, so, why do you write here? Go ahead and fix BLESSED, make it the default, etc. I have enough of your (not referred to you particulary but to the people which contributed to this and other thread) to not be able to respect others opinion. As I said I cannot forbid you guys from doing anything, just go ahead, write the code and commit it, albeit completely bypassing other people's opinion. Attilio -- Peace can only be achieved by understanding - A. Einstein