From owner-freebsd-bugs  Wed Aug  2 12:13:27 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id MAA25401
          for bugs-outgoing; Wed, 2 Aug 1995 12:13:27 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id MAA25394
          for <bugs@freebsd.org>; Wed, 2 Aug 1995 12:13:26 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.11/8.6.5) with ESMTP id MAA01057; Wed, 2 Aug 1995 12:12:50 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id MAA00831; Wed, 2 Aug 1995 12:14:08 -0700
Message-Id: <199508021914.MAA00831@corbin.Root.COM>
To: terry@cs.weber.edu (Terry Lambert)
cc: graichen@omega.physik.fu-berlin.de, bugs@freebsd.org
Subject: Re: please ... 
In-reply-to: Your message of "Wed, 02 Aug 95 12:54:27 MDT."
             <9508021854.AA08742@cs.weber.edu> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 02 Aug 1995 12:14:08 -0700
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.

   Perhaps, but you certainly haven't looked closely at the problem he
reported. The panic is in vn_open and looks identical to the failure I fixed
some time back.

>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.

   Yes, the patch looks interesting. I'm uncertain about the VOP_LOCK around
the call to VFS_VGET, but I suppose that this might protect the mount point
from going away. I'll look into this further.

-DG