trace_landl...eate_ruleset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ trace_landl...eate_ruleset(9)

okay bestie, welcome to the Kernel API Manual ✨ this one's a trace event page and it's honestly so chill β€” let's get into it πŸ’…


🌸 NAME 🌸

trace_landlock_create_ruleset β€” new ruleset created, periodt πŸŽ€


✨ SYNOPSIS ✨

void trace_landlock_create_ruleset (const struct landlock_ruleset
*ruleset );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ruleset β€” the newly created ruleset, and ngl it is never NULL (guard rails, we love to see it 🫢). At this point it hasn't been shared via an fd yet, so no lock is needed β€” lowkey the calmest moment this struct will ever have πŸ’€

πŸ”₯ DESCRIPTION πŸ”₯

So this event is emitted by sys_landlock_create_ruleset while the brand-new ruleset is still private to the calling thread πŸ‘‘ it happens before the file descriptor gets installed, which means it literally cannot race a concurrent close(2) πŸ˜­πŸ™ˆ slay.

It's balanced by a matching landlock_free_ruleset event β€” they're a matching set, iykyk πŸ’–


🌈 SEE ALSO 🌈


πŸ’Œ that's the whole page babes, go forth and trace responsibly πŸ§šβ€β™€οΈ

kisses, this was ./include/trace/events β€” October 2026 edition πŸ“β­

πŸ“¦ where this page comes from