Lines Matching +full:vs +full:- +full:p +full:- +full:supply

43  * ask for the latter, but if you use the Ubuntu nfs4-acl-tools
48  *  - Lustre uses "trusted.*", with "*" matching "lov", "lma",
52  *  - ceph has a name tree of the form "ceph.<type>.<name>" with
56  *  - ext4 uses the POSIX names, plus some special ext4-specific
59  *  - NFS uses both the POSIX names and the NFSv4 ACLs.  However,
63  *    lets nfs4-acl-tools read and write the system.nfs4_acl xattr
68  *  - "security.*" and "selinux.*" are reserved.
70  *  - "security.capability" is the name for capabilities.
72  *  - sockets use "system.sockprotoname".
95  * It's the responsibility of the back-end to supply the ACL
97  * system-specific form.  It's the responsibility of some
98  * (system-specific) code to translate it to *this* form, after
103  * The reason for all this faffing-about with formats is so that
104  * we can *report* the ACLs using Linux 9p style xattrs.
117  *   - a type: allow, deny, audit, alarm
118  *   - a set of flags
119  *   - permissions bits: a "mask"
120  *   - an optional, nominally-variable-length identity
125  * very large, actually-variable-size values; we'll deal with
183  * vs L9P_ACE_LIST_DIRECTORY, for instance.
191 	gid_t	*aca_groups;		/* the additional group-set, if any */
192 	size_t	aca_ngroups;		/* number of groups in group-set */
221  *  - An operation.  This should usually be just one bit from the
222  *    L9P_ACE_* bit-sets above, or our special L9P_ACOP_UNLINK.
223  *    For a few file-open operations it may be multiple bits,
225  *  - The identity of the accessor: uid + gid + gid-set.
226  *  - The type of access desired: this may be multiple bits.
227  *  - The parent directory, if applicable.
228  *  - The child file/dir being accessed, if applicable.
229  *  - stat data for parent and/or child, if applicable.
239  * When falling back to POSIX ACL or Unix-style permissions
291  * These are the system-specific converters.