update_policy(9)

✨ NAME ✨

okay so bestie, this page is update_policy(9), and yes, we're in the Kernel API Manual — hi, hello, welcome to the group chat 💅

update_policy — Write handler for "ipe/policies/$name/update". That's the whole vibe fr fr.

---

📜 SYNOPSIS 📜

ssize_t update_policy (struct file *f , const char __user *data , size_t
len , loff_t *offset );

---

🧚 ARGUMENTS 🧚

• f — Supplies a file structure representing the securityfs node. Basically it hands you the file struct for that securityfs node, periodt.
• data — Supplies a buffer passed to the write syscall. It's the buffer that got passed to the write syscall, no cap.
• len — Supplies the length of data. Literally how long the data is.
• offset — unused. Not used. At all. Bestie, it's just sitting there 😭

---

💖 DESCRIPTION 💖

On success, this updates the policy represented by $name, in-place. That's it, that's the whole lore: success = policy gets updated right where it is, in-place. Slay ✨

---

🎀 RETURN 🎀

• Length of buffer written — Success 👑
• -EPERM — Insufficient permission
• -ENOMEM — Out of memory (OOM)
• -ENOENT — Policy was deleted while updating
• -EINVAL — Policy name mismatch
• -ESTALE — Policy version too old

bestie, those negative returns are the drama — read them carefully before you assume it worked 💀

---

🦋 SEE ALSO 🦋

Kernel file ./security/ipe/policy_fs.c struct ipefs_file(9), read_pkcs7(9), read_policy(9), read_name(9), read_version(9), setactive(9), getactive(9), delete_policy(9), ipe_del_policyfs_node(9), ipe_new_policyfs_node(9) — go read the whole friend group, iykyk 🌸

---

xoxo 💖 from the ./security/ipe source, October 2026 — mwah, periodt 🫶