trace_landl...k_rule_inode(9)
π trace_landlock_check_rule_inode(9) π
okay bestie so this is a page straight out of the Kernel API Manual, section 9 (the kernel-functions girly section, iykyk), and it's all about the trace event trace_landlock_check_rule_inode. yes the header up top truncates it to trace_landl...k_rule_inode(9) bc apparently even manual pages have a character limit π β but the real full name is right there in the NAME section, slay.
β¨ NAME β¨
trace_landlock_check_rule_inode β the inode rule that gets evaluated during an access check π¦
πΈ SYNOPSIS πΈ
void trace_landlock_check_rule_inode (const struct landlock_domain
*domain , const struct landlock_rule *rule , u64 access_request , const
struct dentry *dentry );
π ARGUMENTS π
domainβ the enforcing domain. she is neverNULL, periodt. main character energy, always present β¨ruleβ the matching rule, and it's got per-layer access masks. also neverNULLπaccess_requestβ the access mask being evaluated against the rule. and like, plot twist: during rename/link double-checks this is the domain's handled mask πdentryβ the filesystem dentry that's getting checked. neverNULLeither, we stan a fully-populated argument list π«Ά
π DESCRIPTION π
so basically this trace event gets emitted for each rule that matches during a filesystem access check π₯ like, every single matching rule gets its moment, no gatekeeping.
the grants array is the iconic part β it shows the requested rights that the rule grants at each domain layer π so you can literally see the vibes of the permission at every layer.
if you're sitting there like "bestie how do i even read this," go check Documentation/trace/events-landlock.rst β it explains how to interpret it, no cap π
π¦ SEE ALSO π¦
- Kernel file
./include/trace/events/landlock.hLandlock 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_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)
and that's the whole page, bestie π§π this lil icon comes to you from ./include/trace/events, dated October 2026, roll credits πβ ngl the kernel documentation team ate with this one π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms