tomoyo_update_path_acl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tomoyo_update_path_acl β€” kernel API manual, section 9 πŸŽ€

okay so bestie, welcome to tomoyo_update_path_acl(9) β€” yes that's the whole name, yes it's a mouthful, no we're not shortening it, it's iconic like that ✨


🌸 NAME 🌸

tomoyo_update_path_acl β€” update the "struct tomoyo_path_acl" list. that's it. that's the whole job. she updates the list. periodt πŸ’…


✨ SYNOPSIS ✨

int tomoyo_update_path_acl (const u16 perm , struct tomoyo_acl_param *param );

literally just look at her. two args, one return. clean. minimal. main character energy πŸ”₯


πŸ¦‹ ARGUMENTS πŸ¦‹

  • perm β€” the permission. it's a const u16, she's little but she matters πŸ’–
  • param β€” a pointer to "struct tomoyo_acl_param". yes the quotes are part of the original vibe, don't come for me πŸ™ˆ

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea πŸ“ she returns 0 on success, and a negative value otherwise. that's the whole contract, no cap.

⚠️ okay important one: the caller holds tomoyo_read_lock. that's not optional, that's not a suggestion, that's the rule. the caller is holding it. don't be weird about it πŸ’€

🧚 SEE ALSO 🧚

the kernel file is ./security/tomoyo/file.c and honestly the whole friend group is here β€” say hi to everybody 🫢:

like, thirty-five besties. the group chat is POPPING 🌈


that's the whole page, bestie β€” stay hydrated, hold your read lock, and slay πŸ’œ

from ./security/tomoyo, dated October 2026, and yes she signs off as tomoyo_update_path_acl(9) every single time because consistency is a flex πŸ‘‘βœ¨

πŸ“¦ where this page comes from