selinux_getselfattr(9)

💅 selinux_getselfattr(9) 💅

okay so bestie, this page is from the Kernel API Manual, and it's literally the “get my own SELinux task attributes” girlie. Tiny page, important vibes. Let's go ✨

🌸 NAME 🌸

selinux_getselfattr - Get SELinux current task attributes

🦋 SYNOPSIS 🦋

int selinux_getselfattr (unsigned int attr , struct lsm_ctx __user *ctx
, u32 *size , u32 flags );

🎀 ARGUMENTS 🎀

• attr — the requested attribute. You're telling her which one you want, periodt.
• ctx — buffer to receive the result. This is the user space cutie that gets filled with the goods.
• size — buffer size (input), buffer size used (output). So it's giving input-then-output energy, iykyk.
• flags — unused. Not me checking it anyway; it's literally unused 💀

💖 DESCRIPTION 💖

So what she does is fill the passed user space ctx with the details of the requested attribute. That's the whole job. No cap.

She returns the number of attributes on success, and an error code otherwise. And the tea is: there will only ever be one attribute. Just one. Singular. One-attribute energy 💅

👑 SEE ALSO 👑

Kernel file ./security/selinux/hooks.c, plus these function besties:

• selinux_secmark_enabled(9)
• selinux_peerlbl_enabled(9)
• task_avdcache_reset(9)
• task_avdcache_search(9)
• task_avdcache_update(9)
• selinux_inode_permission(9)
• selinux_inode_xattr_skipcap(9)
• selinux_mmap_backing_file(9)
• selinux_skb_peerlbl_sid(9)
• selinux_conn_sid(9)
• selinux_uring_override_creds(9)
• selinux_uring_sqpoll(9)
• selinux_uring_cmd(9)
• selinux_uring_allowed(9)

mwah 💋 that's the page, bestie. Source/version situation is ./security/selinux, dated October 2026, and yes the page itself is selinux_getselfattr(9) — slay and goodbye 🫶✨