landlock_trace_free_domain(9)
π 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 π
- Kernel file
./security/landlock/trace.c landlock_trace_denial(9)
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
- 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