security_task_prctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

security_task_prctl β€” handle an LSM specific prctl() call.

Okay so this is security_task_prctl(9), straight out of the Kernel API Manual, and bestie it is exactly what it says on the tin: LSM-specific prctl() handling energy ✨


🌸 SYNOPSIS 🌸

int security_task_prctl (int option , unsigned long arg2 , unsigned long
       arg3 , unsigned long arg4 , unsigned long arg5 );

πŸŽ€ ARGUMENTS πŸŽ€

  • option β€” the operation πŸ‘€
  • arg2 β€” argument 🫢
  • arg3 β€” argument 🫢
  • arg4 β€” argument 🫢
  • arg5 β€” argument 🫢

✨ DESCRIPTION ✨

Handle lsm specific prctl operations. That's the assignment, no cap πŸ’…


πŸ”₯ RETURN πŸ”₯

Return -ENOSYS if no-one wanted to handle this op 😭 Any other value? That value causes prctl to return immediately with that value. Periodt.


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./security/security.c β€” and the whole extended universe of friends:


Source/version/date tea for the sign-off, bestie: ./security Β· October 2026 Β· and yes, the page is still security_task_prctl(9) πŸ’… Go forth and handle those LSM specific prctl ops, ily βœ¨πŸ¦‹

πŸ“¦ where this page comes from