From owner-freebsd-current@FreeBSD.ORG Tue Sep 5 19:53:20 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EB1F16A512 for ; Tue, 5 Sep 2006 19:53:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CF5F43D79 for ; Tue, 5 Sep 2006 19:52:15 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k85JplKh069829; Tue, 5 Sep 2006 15:51:48 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 5 Sep 2006 15:38:49 -0400 User-Agent: KMail/1.9.1 References: <44FC1188.7050600@cisco.com> <44FC166B.2060809@cisco.com> In-Reply-To: <44FC166B.2060809@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609051538.50339.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 05 Sep 2006 15:51:48 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1806/Tue Sep 5 11:00:48 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Randall Stewart Subject: Re: Interesting lock issue mtx_flags = 0x6? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2006 19:53:20 -0000 On Monday 04 September 2006 08:04, Randall Stewart wrote: > Never mind.. I think I just figiured it out.. its > a foo-bar on my part :-D Yeah, that constant is MTX_DESTROYED which is written into mtx_lock in mtx_destroy() so that any later mtx_lock's will hang or panic. :) -- John Baldwin