VOP_REVOKE(9)

💅 VOP_REVOKE(9) — the kernel dev manual, bestie edition

okay so real talk, this one's from the Kernel Developer's Manual and it's all about taking access away from a device. dramatic? yes. necessary? also yes. let's get into it 🎀

---

✨ NAME ✨

VOP_REVOKE — revoke access to a device and its aliases

like, all of it. the whole vibe. gone. 🔥

---

🌸 SYNOPSIS 🌸

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

int
VOP_REVOKE(struct vnode *vp, int flags);

yes bestie, both includes, don't skip either one, sys/param.h and sys/vnode.h 💖

---

🦋 DESCRIPTION 🦋

okay so VOP_REVOKE() does a little administrative slay: it revokes access to the device specified by vp, and also to any aliases that were created via make_dev_alias(9). all of them. the whole friend group 💅

and like, after that? any further file operations on any of these devices by processes that have them open will nominally fail. not me ruining everyone's day 😭 but that's literally the point.

the flags must be set to REVOKEALL to signify that all access will be revoked. any other value is invalid — like, don't try it, it's not a vibe check you're gonna pass 🙈

---

🔒 LOCKS 🔒

the vp must be exclusively locked on entry, and it will remain locked upon return. so it goes in locked, it comes out locked — main character energy, no cap ✨

---

👑 SEE ALSO 👑

• make_dev_alias(9)
• vnode(9)

go read them, iykyk 🫶

---

💜 AUTHORS 💜

this manual page was written by Brian Fundakowski Feldman. thank you icon, we appreciate you 🌈⭐

---

k bye bestie, go revoke something responsibly 💖✨🎀🦋🌸💅🫶😭🔥👑🌈⭐💀🙈🍓🧚💜

this page came to you from Debian, dated June 20, 2019 — mwah, mwah, periodt 🎀