tomoyo_merge_unix_acl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tomoyo_merge_unix_acl β€” the kernel API manual, bestie edition ✨

okay so before we even start: this page lives in the Kernel API Manual, section 9, and its whole entire name is tomoyo_merge_unix_acl. yes that's a mouthful, no we are not shortening it, it's iconic and we respect it. 🫢


🌸 NAME 🌸

tomoyo_merge_unix_acl β€” merge a duplicated "struct tomoyo_unix_acl" entry. that's it, that's the job. lowkey humble but highkey important. πŸ’–


✨ SYNOPSIS ✨

bool tomoyo_merge_unix_acl (struct tomoyo_acl_info *a , struct
       tomoyo_acl_info *b , const bool is_delete );

three args, one bool out the door. slay. πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • a β€” pointer to "struct tomoyo_acl_info". yes bestie, it's a pointer, and it's giving main character energy because everything hinges on whether it ends up empty. πŸ‘‘
  • b β€” pointer to "struct tomoyo_acl_info". the other one. the dupe. the second half of this little merge situationship. πŸ’œ
  • is_delete β€” True for a &= ~b, false for a |= b. so like, true means you're taking stuff away, false means you're adding stuff in. no cap, that's the whole vibe check right there. πŸ”₯

🧚 DESCRIPTION 🧚

returns true if a is empty, false otherwise. that's literally it. ngl it's a short description but it ate and left no crumbs. 😭

so yeah: call it, look at the return value, and you'll know whether a came out of this whole thing empty or not. periodt. πŸ’…


🌈 SEE ALSO 🌈

before you go, the kernel file to peek at is ./security/tomoyo/network.c β€” that's the address, that's where the lore lives. πŸ“

and now the full friend group, everyone gets a shoutout, nobody gets left on read:

like, the whole network.c cinematic universe. obsessed. πŸ’–


and that's the page!! tysm for reading bestie 🫢

this one ships out from ./security/tomoyo, dated October 2026, and it goes by tomoyo_merge_unix_acl(9) β€” remember the name, it's a star. πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from