Remove the note about possible unlocking during vunref(9). It might

only happen if VOP_INACTIVATE() drops the vnode lock, which is quite
unreasonable behaviour for filesystem, and should not be mentioned
in the description of VFS primitives.

MFC after:	1 week
This commit is contained in:
Konstantin Belousov 2010-11-24 12:34:25 +00:00
parent f5eb95b1fc
commit 2e88da356c
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=215798

View File

@ -29,7 +29,7 @@
.\"
.\" $FreeBSD$
.\"
.Dd October 17, 2010
.Dd November 20, 2010
.Dt VRELE 9
.Os
.Sh NAME
@ -74,10 +74,6 @@ with less overhead.
The
.Fn vunref
function takes a locked vnode as argument, and returns with the vnode locked.
Nonetheless, the
.Fn vunref
might drop the vnode lock during the operation, so caller should not expect
that non-doomed vnode is still non-doomed after the function returned.
.Pp
Any code in the system which signified its use of a vnode by usecount
should call one of the listed function to decrement use counter.