tomoyo_update_policy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– tomoyo_update_policy(9) β€” like, the glow-up era of the Kernel API Manual ✨

okay so bestie, buckle up πŸŽ€ this one's from the Kernel API Manual and it's literally all about updating an entry for exception policy. short page, yes, but every single crumb matters, so let's not skip a thing πŸ’…


🌸 NAME 🌸

tomoyo_update_policy β€” update an entry for exception policy, no cap πŸ’«


✨ SYNOPSIS ✨

int tomoyo_update_policy (struct tomoyo_acl_head *new_entry , const int
size , struct tomoyo_acl_param *param , bool (*check_duplicate)(const
struct tomoyo_acl_head *, const struct tomoyo_acl_head *) );

like, that's the whole signature, she's a little long but she ate 🫢 keep it exactly as-is, okay?


πŸ¦‹ ARGUMENTS πŸ¦‹

  • new_entry β€” pointer to "struct tomoyo_acl_info". yes, the quotes are part of the lore πŸ™ˆ
  • size β€” the size of new_entry, measured in bytes πŸ“
  • param β€” pointer to "struct tomoyo_acl_param" πŸ’œ
  • check_duplicate β€” a callback function whose whole job is finding duplicated entries πŸ‘‘ (iconic behaviour, honestly)

πŸ’€ DESCRIPTION πŸ’€

So here's the vibe check: it returns 0 on success, and a negative value otherwise 😭 that's it, that's the return contract, fr fr.

Also β€” and this is the important bit β€” the caller holds tomoyo_read_lock πŸ”₯ like, that's a given going in, not something this function does for you. noted. πŸ’…

no extra lore was provided beyond this, so I'm not gonna invent any, bestie 🧚 that's the whole description, periodt.

🌈 SEE ALSO 🌈

like a whole friend group, honestly 🫢 all from the Kernel file ./security/tomoyo/domain.c:


and that's the page!! πŸ’–βœ¨ little sign-off for you: this one lives in ./security/tomoyo and it's dated October 2026 πŸŽ€ so yes, future-coded queen behavior. go forth and update those policy entries, bestie πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from