summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2010-11-24 12:34:25 +0000
committerkib <kib@FreeBSD.org>2010-11-24 12:34:25 +0000
commit545c74c108d341dc6bb0a5ed4c32265504bf14d4 (patch)
tree36a7cdbc347ec6162295ae80268ff9bcf13904fb /share
parent87501c4bfefe33b233bd5e4f18fc8cb483a689a2 (diff)
downloadFreeBSD-src-545c74c108d341dc6bb0a5ed4c32265504bf14d4.zip
FreeBSD-src-545c74c108d341dc6bb0a5ed4c32265504bf14d4.tar.gz
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
Diffstat (limited to 'share')
-rw-r--r--share/man/man9/vrele.96
1 files changed, 1 insertions, 5 deletions
diff --git a/share/man/man9/vrele.9 b/share/man/man9/vrele.9
index 0b9b736..d29ca5b 100644
--- a/share/man/man9/vrele.9
+++ b/share/man/man9/vrele.9
@@ -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.
OpenPOWER on IntegriCloud