From owner-freebsd-current  Tue Sep 23 22:13:26 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA01182
          for current-outgoing; Tue, 23 Sep 1997 22:13:26 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA01175
          for <current@FreeBSD.ORG>; Tue, 23 Sep 1997 22:13:22 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA20124;
	Tue, 23 Sep 1997 22:15:22 -0700 (PDT)
Message-Id: <199709240515.WAA20124@implode.root.com>
To: KATO Takenori <kato@migmatite.eps.nagoya-u.ac.jp>
cc: current@FreeBSD.ORG
Subject: Re: Daily SNAPshots at current.freebsd.org shut down for now. 
In-reply-to: Your message of "Wed, 24 Sep 1997 12:58:32 +0900."
             <199709240358.MAA04770@gneiss.eps.nagoya-u.ac.jp> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 23 Sep 1997 22:15:22 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> To undo the change in 1.49/1.41.2.1 of /sys/dev/vn/vn.c may hide the
>> panic.  But, I think this is NOT real fix.
>
>I made patches for current and 2.2.  They are better than undoing.
>Should they be committed?

   What is wrong with using LK_CANRECURSE ?  In any case, the exact cause
of the recursive locking needs to be understood before this sort of change
is made.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project