From owner-freebsd-bugs  Wed Aug  2 12:02:54 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id MAA25120
          for bugs-outgoing; Wed, 2 Aug 1995 12:02:54 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16])
          by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id MAA25111
          for <bugs@freebsd.org>; Wed, 2 Aug 1995 12:02:53 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA08742; Wed, 2 Aug 95 12:54:28 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9508021854.AA08742@cs.weber.edu>
Subject: Re: please ...
To: davidg@Root.COM
Date: Wed, 2 Aug 95 12:54:27 MDT
Cc: graichen@omega.physik.fu-berlin.de, bugs@freebsd.org
In-Reply-To: <199508021032.DAA00482@corbin.Root.COM> from "David Greenman" at Aug 2, 95 03:32:14 am
X-Mailer: ELM [version 2.4dev PL52]
Sender: bugs-owner@freebsd.org
Precedence: bulk

> >... can anybody look at our problem i posted a week before - here is the post
> >again - the debug kernel and kernel crash dump can be found at:
> 
>    I'm pretty sure that your bug has already been fixed. I think it is caused
> by the VOP_GETATTR() call failing at the wrong time. If it is possible for you
> to update your sources to 2.1-stable via SUP or via FTP by getting the 7/26
> snapshot, then please do so.

Please see my recent patch.  When it comes to file systems, I honestly *do*
know what the hell I'm doing.  Really.

The patch fixes two VOP_GETATTR lock instances, though only one or the
other can bite you depending on the protocol rev you are using.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.