security_compute_av(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ security_compute_av(9) ✨

okay so bestie, welcome to the security_compute_av page from the Kernel API Manual β€” yes it's a section 9 manpage, we love a kernel-internals moment πŸ’…


🌸 NAME 🌸

security_compute_av β€” literally computes access vector decisions. that's the whole vibe. no cap. πŸ”₯


πŸ¦‹ SYNOPSIS πŸ¦‹

void security_compute_av (u32 ssid , u32 tsid , u16 orig_tclass , struct
       av_decision *avd , struct extended_perms *xperms );

copy it exactly, don't be weird about it 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • ssid β€” the source security identifier, iykyk πŸ’–
  • tsid β€” the target security identifier, the other half of the pair ✨
  • orig_tclass β€” the target security class, keep the name orig_tclass, we do not rename things here πŸŽ€
  • avd β€” the access vector decisions get written here, main character energy πŸ‘‘
  • xperms β€” extended permissions, yes it's a struct extended_perms * 🌈

πŸ’œ DESCRIPTION πŸ’œ

So the way that this works: it computes a set of access vector decisions based on the SID pair (ssid, tsid) for the permissions in tclass. that's it, that's the function. it's giving "policy engine doing policy engine things" and honestly? obsessed. ⭐

note that the parameter in the description is written tclass while the synopsis calls it orig_tclass β€” that's what the page says, so that's what we're saying, don't @ me πŸ™ˆ


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./security/selinux/ss/services.c β€” plus the whole friend group, all of these, in this order, exactly:


πŸ’– and that's the page!! πŸ’– shoutout to the source dir ./security/selinux/ss and the date October 2026 β€” that's the sign-off bestie, mwah πŸ’‹βœ¨πŸ¦‹

πŸ“¦ where this page comes from