trace_landlock_free_ruleset(9)

💖 trace_landlock_free_ruleset(9) 💖

okay bestie, this page is straight out of the Kernel API Manual, and it's the whole vibe on trace_landlock_free_ruleset — literally the “ruleset freed” moment ✨

🌈 NAME 🌈

trace_landlock_free_ruleset — Ruleset freed 💅

🎀 SYNOPSIS 🎀

void trace_landlock_free_ruleset (const struct landlock_ruleset *ruleset
);

🦋 ARGUMENTS 🦋

• ruleset — the Ruleset being freed (never NULL); it's at its last reference, so no lock is needed. 🫶

💜 DESCRIPTION 💜

This one is emitted when a ruleset's last reference is dropped — typically when the creating process closes the ruleset file descriptor. it's giving cleanup era, no cap 😭

It fires even when file-descriptor installation failed after creation, keeping the create/free pair balanced. the create/free duo stays iconically balanced 💅✨

🌟 SEE ALSO 🌟

The whole squad is right here, bestie:

• Kernel file ./include/trace/events/landlock.h — Landlock trace events(9)
• trace_landlock_create_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_check_rule_net_port(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)

okay that's the whole page, bestie 💖 source/version is ./include/trace/events, the date is October 2026, and trace_landlock_free_ruleset(9) is out here signing off. mwah 🫶💅