From 609f54c951188af186c30e759ae8b70731e6cbae Mon Sep 17 00:00:00 2001 From: dillon Date: Fri, 24 Sep 1999 07:07:02 +0000 Subject: Update errors in documentation for various VOP_ calls. Specifically, describe the correct locking state expected on entry and return. --- share/man/man9/VOP_INACTIVE.9 | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'share/man/man9/VOP_INACTIVE.9') diff --git a/share/man/man9/VOP_INACTIVE.9 b/share/man/man9/VOP_INACTIVE.9 index 95d21db..e9546ef 100644 --- a/share/man/man9/VOP_INACTIVE.9 +++ b/share/man/man9/VOP_INACTIVE.9 @@ -59,6 +59,14 @@ It can be used to reclaim space for 'open but deleted' files. is called when a vnode is being reused for a different filesystem. Any filesystem specific resources associated with the vnode should be freed. +.Sh LOCKS +.Pp +For VOP_INACTIVE, the vp will be locked on entry. Your VOP_INACTIVE code +must unlock the vp prior to returning. +.Pp +For VOP_RECLAIM, the vp will not be locked on entry and should be left +unlocked on return. +.Pp .Sh PSEUDOCODE .Bd -literal int @@ -70,6 +78,7 @@ vop_inactive(struct vnode *vp) */ ...; } + VOP_UNLOCK(vp, 0, p); return 0; } -- cgit v1.1