From owner-cvs-src@FreeBSD.ORG Fri Sep 2 20:57:44 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 098DF16A41F; Fri, 2 Sep 2005 20:57:44 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36B3943D45; Fri, 2 Sep 2005 20:57:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j82LAmFS030167; Fri, 2 Sep 2005 15:10:48 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4318BCB5.5050001@samsco.org> Date: Fri, 02 Sep 2005 14:57:25 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200509022021.j82KLnZ4076136@repoman.freebsd.org> In-Reply-To: <200509022021.j82KLnZ4076136@repoman.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_mutex.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 20:57:44 -0000 John Baldwin wrote: > jhb 2005-09-02 20:21:49 UTC > > FreeBSD src repository > > Modified files: > sys/kern kern_mutex.c > Log: > - Add an assertion to panic if one tries to call mtx_trylock() on a spin > mutex. Explaining exactly why this is bad, either in a commit log, in a manpage, or in source code comments would be really nice. The pitfalls are not immediately obvious to the casual observer. > - Don't panic if a spin lock is held too long inside _mtx_lock_spin() if > panicstr is set (meaning that we are already in a panic). Just keep > spinning forever instead. If panicstr is set, shouldn't all CPUs have already been sent an NMI? This seems like a step backwards in reliability. Scott