o Bring VOP_GETACL(9) and VOP_GETEXTATTR(9) man page "LOCKS" sections in

  sync with the implementation.  Vnode locks *are* required for these
  operations, as some underlying implementations will require them.

Obtained from:	TrustedBSD Project

2 files changed, 2 insertions, 4 deletions

diff --git a/share/man/man9/VOP_GETACL.9 b/share/man/man9/VOP_GETACL.9
index 244d666..8a6350e 100644
--- a/share/man/man9/VOP_GETACL.9
+++ b/share/man/man9/VOP_GETACL.9
@@ -67,8 +67,7 @@ directory ACL interfaces.  More information about ACL management in kernel
 may be found in
 .Xr acl 9 .
 .Sh LOCKS
-No locks are required to call this vnode method, and any locks held on
-entry will be held on exit.
+The vnode will be locked on entry and should remain locked on return.
 .Sh RETURN VALUES
 If the
 .Fa aclp
diff --git a/share/man/man9/VOP_GETEXTATTR.9 b/share/man/man9/VOP_GETEXTATTR.9
index 5db01cb..b3e4cc0 100644
--- a/share/man/man9/VOP_GETEXTATTR.9
+++ b/share/man/man9/VOP_GETEXTATTR.9
@@ -66,8 +66,7 @@ Extended attribute semantics may vary by file system implementing the call.
 More information on extended attributes may be found in
 .Xr extattr 9 .
 .Sh LOCKS
-No locks are required to call this vnode method, and any locks held on
-entry will be held on exit.
+The vnode will be locked on entry and should remain locked on return.
 .Sh RETURN VALUES
 On success, zero will be returned, and the uio structure will be updated to
 reflect data read.  Otherwise, an appropriate error code is returned.