Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Aug 1995 12:14:08 -0700
From:      David Greenman <davidg@Root.COM>
To:        terry@cs.weber.edu (Terry Lambert)
Cc:        graichen@omega.physik.fu-berlin.de, bugs@freebsd.org
Subject:   Re: please ... 
Message-ID:  <199508021914.MAA00831@corbin.Root.COM>
In-Reply-To: Your message of "Wed, 02 Aug 95 12:54:27 MDT." <9508021854.AA08742@cs.weber.edu> 

next in thread | previous in thread | raw e-mail | index | archive | help
>> >... 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508021914.MAA00831>