getenforce(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

getenforce(9) πŸ’…

okay so this page is from the Kernel API Manual, and it’s about a kernel read handler. bestie, it’s giving securityfs energy, no cap. ✨

πŸ’– NAME πŸ’–

getenforce β€” read handler for the securityfs node, "ipe/enforce". yes, that’s literally the whole vibe. πŸ¦‹

🌸 SYNOPSIS 🌸

here’s the signature β€” keep it exact, bestie:

ssize_t getenforce (struct file *f , 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 read syscall. ✨
  • len β€” supplies the length of data. πŸŽ€
  • offset β€” unused. periodt, it just sits there. πŸ’€

πŸ”₯ RETURN πŸ”₯

the return value is Length of buffer written β€” that’s it, that’s the tea. πŸ‘‘

🌈 SEE ALSO 🌈

Kernel file ./security/ipe/fs.c, plus the whole squad: setaudit(9), getaudit(9), setenforce(9), new_policy(9), ipe_init_securityfs(9) 🫢


🫢 signing off, bestie β€” source/version: ./security/ipe; date: October 2026; page: getenforce(9) πŸŽ€

πŸ“¦ where this page comes from