label_merge_insert(9)

📦 version 7.3.1, in nixpkgs unstable

💅 label_merge_insert(9) — a Kernel API Manual moment 🎀

okay so bestie, we're in label_merge_insert(9) territory — that's the Kernel API Manual page, and yes it's exactly as niche and exactly as iconic as it sounds ✨

🦋 NAME 🦋

label_merge_insert — create a new label by merging @a and @b 💖

🌸 SYNOPSIS 🌸

struct aa_label * label_merge_insert (struct aa_label *new , struct aa_label *a , struct aa_label *b );

✨ ARGUMENTS ✨

  • new — a preallocated label that we merge into — and no, it is NOT NULL, do not come for me 🙈
  • a — the label that gets merged with b (also NOT NULL, we stay strict 💅)
  • b — the label that gets merged with a (NOT NULL, obviously, consistency is key 🎀)

💜 DESCRIPTION 💜

Requires: preallocated proxy. that's it, that's the whole vibe check 🫶

🔥 RETURN 🔥

it hands you back a ref counted label, and which one you get is giving choose-your-own-adventure:

  • new — if the merge is unique, slay, brand new label for you 👑
  • a — if b is a subset of a, then congrats, a was the moment all along
  • b — if a is a subset of b, then b ate and left no crumbs ⭐

💀 NOTE 💀

lowkey important: it will not use new if the merge results in new == a or b 🫠
and fr fr, this must be used within the labelset write lock — otherwise you're racing with setting labels stale, and that's not the main character energy we're going for 😭

🌈 SEE ALSO 🌈

the kernel file this lives in is ./security/apparmor/label.c — here's your whole reading list bestie, iykyk 📚

and that's the whole page, bestie 🧚 source: ./security/apparmor, dated October 2026 — periodt, go merge some labels 💅💖

📦 where this page comes from