Update man page - directory vnode should not be unlocked or released

by the VOP routine.  The caller does it.
This commit is contained in:
Matthew Dillon 1999-02-13 07:44:14 +00:00
parent ef6caa5169
commit 3ac84fed2e

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id: VOP_LINK.9,v 1.3 1997/04/13 14:48:53 bde Exp $
.\" $Id: VOP_LINK.9,v 1.4 1998/03/12 07:31:11 charnier Exp $
.\"
.Dd July 24, 1996
.Os
@ -46,17 +46,19 @@ Its arguments are:
.Bl -tag -width 8X
.It Ar dvp
the vnode of the directory
.It At vp
.It Ar vp
the vnode of the file to be linked
.It Ar cnp
pathname information about the file
.El
.Pp
The directory vnode is unlocked and released on exit.
The pathname info must be released on exit. The directory and
file vnodes should NOT be released on exit.
.Sh LOCKS
The directory,
.Fa dvp
should be locked on entry and will be unlocked and released on exit.
should be locked on entry. The caller will unlock and release
it on return so the VOP routine should not.
The file
.Fa vp
should not be locked.