trace_landlo...ule_net_port(9)

💅 trace_landlock_check_rule_net_port — Kernel API Manual, bestie edition 🦋

okay so real talk, this is a (9) page from the Kernel API Manual (yes that's the manual name, we're being ✨official✨ today) and it's all about one iconic little tracepoint: trace_landlock_check_rule_net_port. She's giving "I log things when Landlock checks a network port rule" and honestly? obsessed. 🌸

---

✨ NAME ✨

trace_landlock_check_rule_net_port — network port rule evaluated 👑

like, the trace event that fires when a network port rule gets evaluated. that's the whole vibe. 💅

---

🎀 SYNOPSIS 🎀

void trace_landlock_check_rule_net_port (const struct landlock_domain
*domain , const struct landlock_rule *rule , u64 access_request , u64
port );

no cap, that's the exact signature, spaces and all. don't touch the spacing, she's delicate. 🫶

---

🌈 ARGUMENTS 🌈

• domain — the enforcing domain, aka the main character here. literally never NULL, so don't even try it. 🚫
• rule — the matching rule, carrying per-layer access masks. also never NULL. two for two on the "never NULL" agenda, we love a consistent queen. 👑
• access_request — the access mask being requested. that's the ask. 📨
• port — the network port being checked, in host endianness (yes, host. not network. don't @ me). 🔌

---

💖 DESCRIPTION 💖

so this one is emitted for each rule that matches during a network access check. every single match, she's there. 🌟

the grants array shows the requested rights the rule grants at each domain layer — it's basically a little receipt of who's allowed what at every level. 🧾

and if you're sitting there like "okay but how do I actually read that array" — the manual says to go see Documentation/trace/events-landlock.rst for how to interpret it. iykyk, go read the docs bestie, it's literally right there. 📖✨

---

🦋 SEE ALSO 🦋

• the kernel file ./include/trace/events/landlock.h — Landlock trace events(9) 💫
• trace_landlock_create_ruleset(9)
• trace_landlock_free_ruleset(9)
• trace_landlock_add_rule_path_beneath(9)
• trace_landlock_add_rule_net_port(9)
• trace_landlock_create_domain(9)
• trace_landlock_enforce_domain(9)
• trace_landlock_free_domain(9)
• trace_landlock_check_rule_inode(9)
• trace_landlock_deny_access_fs(9)
• trace_landlock_deny_access_net(9)
• trace_landlock_deny_ptrace(9)
• trace_landlock_deny_scope_signal(9)
• trace_landlock_deny_scope_abstract_unix_socket(9)

that's the whole friend group right there, go say hi. 💜

---

lowkey a reminder: domain and rule are never NULL in this call. that's not a suggestion, that's the contract. 🫡

---

okay that's the page!! this one came from ./include/trace/events and she's dated October 2026 — so yeah, future icon behavior honestly. mwah, go trace something pretty 💋💖🎀