trace_landlo...scope_signal(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, we're in the Kernel API Manual, section 9, and the header lowkey truncates to trace_landlo...scope_signal(9). the full name is trace_landlock_deny_scope_signal, and the NAME line says: Signal delivery denied by LANDLOCK_SCOPE_SIGNAL. that's the whole page's main character energy. πŸ’…

πŸ› οΈ SYNOPSIS πŸ› οΈ

the signature, verbatim, no edits, no cap:

void trace_landlock_deny_scope_signal (const struct landlock_hierarchy *hierarchy , bool same_exec , bool logged , u64 target_domain_id , const struct task_struct *target , int signal );

πŸ’¬ ARGUMENTS πŸ’¬

okay here's the cast, and every single detail matters:

  • hierarchy β€” the denying domain's hierarchy node, and it is never NULL; its id is the domain field. it always shows up, periodt. πŸ’–
  • same_exec β€” whether the policy subject entered the denying domain itself. yes/no energy, but make it precise. πŸ¦‹
  • logged β€” the domain's audit-logging decision for this denial. basically the "did we log this?" decision. 🌸
  • target_domain_id β€” the target's Landlock domain ID, or 0 if the target is unsandboxed. zero is doing real work here, bestie. ⭐
  • target β€” the task the signal was aimed at, and it is never NULL. target_pid is the init-namespace TGID (like audit's opid). iconic. πŸ‘‘
  • signal β€” the signal selected by the denied check. 0 is a permission probe, not an absent value. do not read zero as "no signal," fr fr. 😭

🌸 DESCRIPTION 🌸

Emitted when a Landlock domain denies signal delivery to a scoped-out target. that's the event, that's the vibe. πŸ’…

πŸ”— SEE ALSO πŸ”—

go read these too, bestie β€” the whole Landlock trace-event family is here:

okay that's the whole page bestie πŸ’… β€” source/version: ./include/trace/events, date: October 2026, and the footer's truncated title is trace_landlo...scope_signal(9). periodt 🫢

πŸ“¦ where this page comes from