From owner-freebsd-current  Mon Oct 20 23:57:02 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA24251
          for current-outgoing; Mon, 20 Oct 1997 23:57:02 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24243
          for <freebsd-current@FreeBSD.ORG>; Mon, 20 Oct 1997 23:56:56 -0700 (PDT)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id QAA07277; Tue, 21 Oct 1997 16:51:05 +1000
Date: Tue, 21 Oct 1997 16:51:05 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199710210651.QAA07277@godzilla.zeta.org.au>
To: joerg_wunsch@uriah.heep.sax.de, kato@migmatite.eps.nagoya-u.ac.jp
Subject: Re: lockmgr panic
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I don't have any idea to solve this problem except:
>
>	a. rewrite delayed write stuff.
>	b. rewrite vn driver.
>	c. apply the patch included in this mail.
>
>The patch from 3.0-current is as follows:

`isvplocked' seems to be used uninitialized.

Someone committed a modified version of this to 2.2 without testing
it in -current (without even committing it to -current).

Bruce