From owner-freebsd-current@FreeBSD.ORG  Tue Aug 21 04:57:41 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0385D16A420;
	Tue, 21 Aug 2007 04:57:41 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id E7A0313C48D;
	Tue, 21 Aug 2007 04:57:40 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196])
	by elvis.mu.org (Postfix) with ESMTP id 57EDE1A3C1A;
	Mon, 20 Aug 2007 21:55:49 -0700 (PDT)
Received: by rot26.obsecurity.org (Postfix, from userid 1001)
	id 3F93AC3EB; Tue, 21 Aug 2007 00:57:40 -0400 (EDT)
Date: Tue, 21 Aug 2007 00:57:40 -0400
From: Kris Kennaway <kris@obsecurity.org>
To: Kostik Belousov <kostikbel@gmail.com>
Message-ID: <20070821045739.GA83774@rot26.obsecurity.org>
References: <200708202340.29678.qpadla@gmail.com>
	<20070820205201.GW2738@deviant.kiev.zoral.com.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070820205201.GW2738@deviant.kiev.zoral.com.ua>
User-Agent: Mutt/1.4.2.3i
Cc: freebsd-current@freebsd.org, rwatson@freebsd.org
Subject: Re: And probably the final crash for today's current :) (panic:
	filesystem goof: vop_panic[vop_print])
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2007 04:57:41 -0000

On Mon, Aug 20, 2007 at 11:52:01PM +0300, Kostik Belousov wrote:

> Quite often, the "impossible" panics with vnode locking are happens
> because some other thread already paniced the kernel. Then, lockmgr
> passes all lock requests without actually locking. I would suggest
> looking around to make sure this is not the case there.

Is there a good reason to be doing that?

Kris