hook_ptrace_access_check(9)
π hook_ptrace_access_check (from the Kernel API Manual, bestie) π
okay so picture this: it's giving security hook, it's giving Landlock, and it's literally the bouncer at the club deciding if one process gets to poke at another πβ¨
πΈ NAME πΈ
hook_ptrace_access_check β the vibe check that decides whether the current process may access another one π«Ά
β¨ SYNOPSIS β¨
int hook_ptrace_access_check (struct task_struct *const child , const
unsigned int mode );
like, that's the whole signature, no notes, she ate π
π ARGUMENTS π
childβ the process being accessed. the one getting snooped on, bestie πmodeβ the mode of attachment. how exactly you're tryna attach, iykyk
π¦ DESCRIPTION π¦
so here's the tea β if the current task has Landlock rules, then child must have at least the same rules. that's it, that's the whole requirement.
and if not? denied. π« lowkey brutal but she's consistent.
π₯ RETURN π₯
0β permission is granted, slay, you're in π-errnoβ denied π the errno tells you why, fr fr
π SEE ALSO π
- Kernel file
./security/landlock/task.c domain_scope_le(9)hook_ptrace_traceme(9)domain_is_scoped(9)
go read those next, they're all connected, no cap π§
π that's the whole page, periodt π
this lil masterpiece lives in the ./security/landlock source (that's the version tag, mwah), dated October 2026, and it's filed under hook_ptrace_access_check(9) in case you need to find her again πβ¨π«Ά
π¦ 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