From owner-freebsd-current  Sun Jul 27 04:29:23 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA27768
          for current-outgoing; Sun, 27 Jul 1997 04:29:23 -0700 (PDT)
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA27763
          for <current@freebsd.org>; Sun, 27 Jul 1997 04:29:21 -0700 (PDT)
Received: from gid.co.uk (uucp@localhost)
          by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP
	  id MAA16491 for freebsd.org!current; Sun, 27 Jul 1997 12:12:35 +0100 (BST)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 27 Jul 1997 12:18:11 +0100
X-Sender: rb@194.32.164.1
Message-Id: <l03020904b000dcab2ebb@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 27 Jul 1997 12:14:10 +0100
To: current@freebsd.org
From: Bob Bishop <rb@gid.co.uk>
Subject: lockstatus() panic: a data point
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

FWIW, I used to be regularly afflicted with the lockstatus panic. I've been
running with the following patch (I forget who from) since 28 May, since
when I haven't had a single occurrence.

Index: ufs_vnops.c
===================================================================
RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v
retrieving revision 1.50
diff -u -r1.50 ufs_vnops.c
--- ufs_vnops.c 1997/05/17 18:32:53     1.50
+++ ufs_vnops.c 1997/05/27 13:11:19
@@ -1788,6 +1788,9 @@
        } */ *ap;
 {

+       if (ap->a_vp->v_flag & VXLOCK)
+               return TRUE;
+
        return (lockstatus(&VTOI(ap->a_vp)->i_lock));


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK