Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!tut.cis.ohio-state.edu!husc6!rice!sun-spots-request
From: prisma!berliner@uunet.uu.net (Brian Berliner)
Newsgroups: comp.sys.sun
Subject: Re: nfs bug in 3.2, 3.5 (
Keywords: SunOS
Message-ID: <3455@kalliope.rice.edu>
Date: 26 May 89 20:25:44 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 4, message 5 of 13

In Sun-Spots Digest v7n304, forsyth@minster.york.ac.uk notes a bug in the
NFS unlink case where the unlinked file is a FIFO special file.  In 3.X
versions of SunOS, this would usually case a kernel panic if the FIFO that
is being unlinked is currently open (3.5 *may* have fixed this... don't
know).

You can be certain that this is fixed properly starting with 4.0.  And the
fix is in fact the correct one; a new vnode operation was added to return
the real vnode pointer, VOP_REALVP(), to correctly get back to an NFS
vnode that has an rnode attached.  So all works well.

					Brian Berliner
					Prisma, Inc.
					berliner@prisma.com