match_mnt_flags(9)

💅 match_mnt_flags — Kernel API Manual, section 9 🎀

okay so bestie, welcome to the match_mnt_flags(9) page ✨ this one's a little function living in the kernel's AppArmor mount code, and honestly? she's doing an ordered match on mount flags, which is kind of the whole plot. let's get into it 🦋

---

✨ SYNOPSIS ✨

aa_state_t match_mnt_flags (const struct aa_dfa *dfa , aa_state_t state
, unsigned long flags );

that's the whole vibe, no cap. three args in, one state out 💅

---

🌸 ARGUMENTS 🌸

• dfa — the dfa you're matching against, bestie. that's the automaton in question 🧚
• state — the state you're starting from. like, where the walk begins ✨
• flags — the mount flags you're matching against. yes, those flags 🎀

---

💖 DESCRIPTION 💖

okay so here's the tea ⭐ mount flags are encoded as an ordered match. and the reason she does that instead of just checking against a simple bitmask? it's giving flexibility, because the ordered-match setup allows for logical operations on the flags 🔥 that's the whole point — a plain bitmask check couldn't do that, so we don't do it. periodt 💅

---

👑 RETURN 👑

the next state after the flags match 💫 that's it, that's the return value, no extra lore 🫶

---

🌈 SEE ALSO 🌈

• Kernel file ./security/apparmor/mount.c (that's where the magic lives 🏠)
• audit_cb(9)
• match_mnt_path_str(9)
• match_mnt(9)

---

lowkey a reminder bestie: this page is from ./security/apparmor, and it's dated October 2026 — so if you're reading this in the future, hey, you're right on time 🌸 mwah, go read the rest of the family, they all slay 💜

---