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
This commit is contained in:
parent
988ee790d4
commit
28994ea06f
@ -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
|
||||
|
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user