tomoyo_path_permission(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌈 tomoyo_path_permission β€” Kernel API Manual 🌈

πŸ’– NAME πŸ’–

tomoyo_path_permission β€” check permission for single path operation. periodt. πŸŽ€


✨ SYNOPSIS ✨

okay bestie, here’s the signature copied exactly so nobody has to squint:

int tomoyo_path_permission (struct tomoyo_request_info *r , u8 operation , const struct tomoyo_path_info *filename );

πŸŽ€ ARGUMENTS πŸŽ€

  • r β€” pointer to struct tomoyo_request_info. yes, that request-info struct, iykyk. πŸ’…
  • operation β€” type of operation. literally the operation type. ✨
  • filename β€” filename to check. the filename to check, no cap. πŸ“

πŸ¦‹ DESCRIPTION πŸ¦‹

Bestie, the whole contract is short and sweet: it returns 0 on success, and a negative value otherwise. that’s the entire return vibe. πŸ’–

Also important, straight from the og: caller holds tomoyo_read_lock. yes, that’s part of the deal β€” don’t forget it. 🌸


πŸ’… SEE ALSO πŸ’…

the kernel file is ./security/tomoyo/file.c, and the friend group is huge β€” every single one of these refs is invited, no skips:


πŸ’– signed off from ./security/tomoyo, October 2026 β€” tomoyo_path_permission(9) out. slay and stay safe, bestie 🫢

πŸ“¦ where this page comes from