Displaying 2 results from an estimated 2 matches for "vop_access".
Did you mean:
pop_access
2007 Sep 03
1
Code/comment mismatch in delegated administration code.
...hould allow the mount. Am I right? If I am right, the patch below
implements my thinking.
--- uts/common/fs/zfs/zfs_vfsops.c
+++ uts/common/fs/zfs/zfs_vfsops.c
@@ -608,11 +608,9 @@
goto out;
}
- if (error = secpolicy_vnode_owner(cr, vattr.va_uid)) {
- goto out;
- }
-
- if (error = VOP_ACCESS(mvp, VWRITE, cr, td)) {
+ if (secpolicy_vnode_owner(cr, vattr.va_uid) != 0 &&
+ VOP_ACCESS(mvp, VWRITE, cr, td) != 0) {
+ error = EPERM;
goto out;
}
--
Pawel Jakub Dawidek http://www.wheel.pl
pjd at FreeBSD.org http://www.F...
2008 Aug 31
0
NFSv4 ACLs.
...ENTRIES was increased from 32 to 204.
Syscall interface remains the same, except for a changed "type" constants,
in order to preserve backwards compatibility with older libc.
VOP_SETACL, VOP_GETACL and VOP_ACLCHECK interface remains the same,
except for modified "struct acl". VOP_ACCESS changed a little - second
argument was changed from "int" to "vaccess_t"; there should be no
functional changes related to that. There are differences related to
permissions granularity; as long as VOP_ACCESS implementation simply
passes the "a_mode" parameter to the...