VOP_SETACL(9)

💅 VOP_SETACL 💅

okay so bestie, welcome to the VOP_SETACL(9) page — the one that's all about setting the access control list (ACL) for a vnode. it's a kernel developer manual, but we're gonna make it make sense, fr fr 💖

---

✨ NAME ✨

VOP_SETACL — set the access control list for a vnode. yup, that's the whole vibe.

---

🌸 SYNOPSIS 🌸

#include <sys/param.h>
#include <sys/vnode.h>
#include <sys/acl.h>

int
VOP_SETACL(struct vnode *vp, acl_type_t type, struct acl *aclp,
    struct ucred *cred, struct thread *td);

like, copy-paste this exactly, no cap 🫶

---

🎀 DESCRIPTION 🎀

so this vnode call is literally how you set the access control list (ACL) for a file or directory. it's giving security gatekeeping energy 👑

here's the breakdown of its arguments, bestie:

• vp — the vnode of the file or directory. like, the actual thing you're touching.
• type — the type of ACL to set. gotta know what flavor you're working with.
• aclp — a pointer to an ACL structure from which to retrieve the ACL data. it's the source of truth.
• cred — the user credentials to use in authorizing the request. who's asking?
• td — the thread setting the ACL. the main character of this operation 💅

now some very important details:

the aclp pointer may be NULL to indicate that the specified ACL should be deleted. so NULL = yeet it 🗑️

the cred pointer may be NULL to indicate that access control checks are not to be performed, if possible. this cred setting might be used to allow the kernel to authorize ACL changes that the active process might not be permitted to make. like, the kernel gets a vip pass, iykyk.

also, real talk: the vnode ACL interface defines the syntax, and not semantics, of file and directory ACL interfaces. more info about ACL management in kernel can be found in acl(9). go read it, bestie.

---

🔒 LOCKS 🔒

the vnode will be locked on entry and should remain locked on return. no unlocking mid-operation, that's messy. periodt.

---

🌈 RETURN VALUES 🌈

if the ACL is successfully set, then zero is returned. slay. otherwise, an appropriate error code is returned. and we list those below 👇

---

💀 ERRORS 💀

• [EINVAL] — the ACL type passed is invalid for this vnode, or the ACL data is invalid. like, wrong vibe entirely.
• [EACCES] — the caller does not have the appropriate privilege. no permission, no entry 🙈
• [ENOMEM] — sufficient memory is not available to fulfill the request. brain empty, no thoughts.
• [EOPNOTSUPP] — the file system does not support VOP_SETACL(). it's just not that girl.
• [ENOSPC] — the file system is out of space. full house, no room.
• [EROFS] — the file system is read-only. can't touch this 🔥

---

🦋 SEE ALSO 🦋

• acl(9)
• vnode(9)
• VOP_ACLCHECK(9)
• VOP_GETACL(9)

go click around, bestie, it's a whole ecosystem 💜

---

👑 AUTHORS 👑

this manual page was written by Robert Watson. iconic behavior, we love to see it 🎀

---

okay that's the whole page! this was the Debian version, dated December 23, 1999 — a vintage slay 💅✨ go forth and set those ACLs, bestie! 🦋🌸