From 2e88da356ce72f7a0f7a56c5ec3a483791a8ffd9 Mon Sep 17 00:00:00 2001
From: Konstantin Belousov <kib@FreeBSD.org>
Date: Wed, 24 Nov 2010 12:34:25 +0000
Subject: [PATCH] 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
---
 share/man/man9/vrele.9 | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/share/man/man9/vrele.9 b/share/man/man9/vrele.9
index 0b9b7361777d..d29ca5b079b0 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.