selinux_uring_allowed(9)
π¦ selinux_uring_allowed(9) β the Kernel API Manual, section 9 π¦
β¨ NAME β¨
selinux_uring_allowed β check if io_uring_setup() can be called. That's it, that's the gig, and honestly? Iconic. π
πΈ SYNOPSIS πΈ
int selinux_uring_allowed (void );
literally the whole signature, no cap. β¨
π ARGUMENTS π
voidβ no arguments, bestie. Zero. None. The function said βI need nobodyβ and meant it. π
π DESCRIPTION π
okay so picture this: you're the current task, and the question on the table is whether you're allowed to call io_uring_setup. This function checks exactly that. It's giving permission vibe check, and the whole point is finding out if the current task can make that call. Lowkey specific, highkey important. β¨
No extra lore in this manpage β it's a focused little check, and it ate. π«Ά
π SEE ALSO π
The lore lives in the Kernel file ./security/selinux/hooks.c, and here's the whole bestie lineup:
- Kernel file
./security/selinux/hooks.c 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_getselfattr(9)selinux_uring_override_creds(9)selinux_uring_sqpoll(9)selinux_uring_cmd(9)
okay that's the page! source/version: ./security/selinux; date: October 2026; page: selinux_uring_allowed(9) from the Kernel API Manual. bye bestie, go check those permissions responsibly. π«Άπβ¨
π¦ 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