new_policy(9)

new_policy(9) 💅✨

okay so bestie, welcome to the Kernel API Manual page for new_policy(9) — yes, kernel-space, 9-section energy. 💖 This one is the write handler for the securityfs node, "ipe/new_policy". no cap.

🎀 NAME

new_policy — the write handler for the securityfs node, "ipe/new_policy". literally its whole job. 💅

✨ SYNOPSIS

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

🦋 ARGUMENTS

• f — supplies a file structure representing the securityfs node.
• data — supplies a buffer passed to the write syscall.
• len — supplies the length of data.
• offset — unused. 🙈

🌈 RETURN

okay so the return value is lowkey the whole plot. here's every outcome, fr fr:

• Length of buffer written — Success. slay. ✅
• -EPERM — Insufficient permission.
• -ENOMEM — Out of memory (OOM).
• -EBADMSG — Policy is invalid.
• -ERANGE — Policy version number overflow.
• -EINVAL — Policy version parsing error.
• -EEXIST — Same name policy already deployed.
• -ENOKEY — Policy signing key not found.
• -EKEYREJECTED — Policy signature verification failed.

👑 SEE ALSO

Kernel file ./security/ipe/fs.c — setaudit(9), getaudit(9), setenforce(9), getenforce(9), ipe_init_securityfs(9). go read those too, bestie. 💜

Signed off with all the receipts: source/version ./security/ipe, date October 2026, manual new_policy(9). mwah 💋🫶