tomoyo_merge...h_number_acl(9)

📦 version 7.3.1, in nixpkgs unstable

✨ tomoyo_merge...h_number_acl(9) ✨

okay bestie, welcome to the Kernel API Manual 🎀 — yes, the title's literally got an ellipsis in it, not me being lazy, that's just how it got truncated and we're rolling with it 💅

💖 NAME 💖

tomoyo_merge_path_number_acl — the function that merges duplicated struct tomoyo_path_number_acl entries. yes, duplicated. we don't do dupes here, we consolidate 🫶

🌸 SYNOPSIS 🌸

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

like, three args, returns a bool, classic. slay ✨

🦋 ARGUMENTS 🦋

  • a — a pointer to struct tomoyo_acl_info. that's the vibe. it's the one being merged into, iykyk 👑
  • b — a pointer to struct tomoyo_acl_info. also iconic. this is the other one in the situationship 🥀
  • is_delete — ok so this one's the main character: true means you're doing a &= ~b, and false means you're doing a |= b. literally just a bool deciding which bitwise direction we're going. no cap 💀

🔥 DESCRIPTION 🔥

Returns true if a is empty, and false otherwise. that's it. that's the whole plot 🙈

the way that's genuinely it — merge the dupes, then tell the caller whether a came out empty. short king of a function, fr fr ⭐

🌈 SEE ALSO 🌈

everything here lives in the kernel file ./security/tomoyo/file.c, and honestly the whole friend group showed up, so let's do roll call 📋💖

like, the entire extended universe. obsessed 🧚💜

ngl bestie, the whole same_* / merge_* / update_* trio pattern is giving boyband, and if you get one of them you basically get all of them. periodt 🔥

k byeeee 💕 this page came from ./security/tomoyo, dated October 2026, and it's filed under tomoyo_merge...h_number_acl(9) — go forth and merge responsibly, mwah 😭💅🍓

📦 where this page comes from