trace_landl...k_rule_inode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 never NULL, periodt. main character energy, always present ✨
  • rule β€” the matching rule, and it's got per-layer access masks. also never NULL πŸ’…
  • 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. never NULL either, 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 πŸ¦‹


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