landlock_trace_free_domain(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie, meet landlock_trace_free_domain(9) from the Kernel API Manual β€” the page for landlock_trace_free_domain: Emit a tracepoint on domain deallocation. πŸ’…βœ¨


✨ SYNOPSIS ✨

void landlock_trace_free_domain (const struct landlock_hierarchy *const
hierarchy );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • hierarchy β€” the domain's hierarchy being deallocated. literally the thing getting freed, bestie 🫢

🌸 DESCRIPTION 🌸

okay so here's the vibe: this fires only for a hierarchy whose creation event was emitted β€” meaning one that left LANDLOCK_LOG_UNCOMMITTED in landlock_restrict_self. no cap. πŸ”₯

the way this keeps the create/free pair balanced is honestly iconic: a hierarchy that never became observable is freed silently, while a domain that landlock_restrict_self created and a thread-sync failure then aborted still fires free_domain, because its creation event already fired. πŸŽ€

called from landlock_log_free_domain. periodt. πŸ’œ


πŸ‘‘ SEE ALSO πŸ‘‘


mwah πŸ’‹ this cutie of a page is brought to you by source/version/date ./security/landlock, October 2026, and the manual itself is landlock_trace_free_domain(9) β€” catch you in the kernel, bestie πŸ«ΆπŸ¦‹

πŸ“¦ where this page comes from