trace_landlo...ule_net_port(9)

📦 version 7.3.1, in nixpkgs unstable

💖 trace_landlock_add_rule_net_port — a network-port rule just landed in a ruleset 🎀

okay so this one's from the Kernel API Manual (that's the manual name, bestie, section 9 — kernel internals, iykyk), and it's literally a tracepoint page. It's giving "backstage pass to the Landlock trace events" energy. Let's go ✨

🌸 SYNOPSIS 🌸

void trace_landlock_add_rule_net_port (const struct landlock_ruleset
*ruleset , u32 flags , u64 access_rights , u64 port );

that's the whole vibe — a void function, four args, no return value, no notes. slay 💅

🦋 ARGUMENTS 🦋

  • ruleset — the source ruleset, and she is never NULL. fr fr, never. 👑
  • flags — the complete, validated landlock_add_rule_flags value that this successful call supplied. heads up tho: this is not the rule's accumulated quiet state, don't get it twisted 🙈
  • access_rights — the canonical per-call access mask that got passed to landlock_insert_rule after normalization. and ngl, it's not the raw sys_landlock_add_rule argument, and it's not the accumulated rule either — it's the post-normalization version, periodt ✨
  • port — the network port in host endianness, forwarded directly from landlock_net_port_attr.port. straight from the source, no detours 🫶

💜 DESCRIPTION 💜

so this tracepoint gets emitted by sys_landlock_add_rule under the modified ruleset's lock 🔒 — which is lowkey the whole point: the reported ruleset is a stable snapshot that no concurrent writer can change. main character stability energy, honestly 💅

the way that lock holds it down so nothing else can sneak in and rewrite the story? iconic. 🎀

🌈 SEE ALSO 🌈

the whole squad is here, we love a full friend group 💖

and that's the page!! 🦋 this little cutie lives at ./include/trace/events and the version/date footer says October 2026 — so yeah, mark your calendar bestie, she's from the future 🎀✨ see u in the next manpage, mwah 💜

📦 where this page comes from