apparmor_uring_sqpoll(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ apparmor_uring_sqpoll β€” the Kernel API Manual moment

okay so real talk, this is a page from the Kernel API Manual (like, the kernel's own group chat of docs) and it's all about apparmor_uring_sqpoll(9). yes bestie, that's a whole mouthful, but it's lowkey iconic once you get it πŸ’…


✨ NAME ✨

apparmor_uring_sqpoll β€” check if a io_uring polling thread can be created

like, it's the vibe-check bouncer at the door of io_uring polling-thread creation πŸŽ€


🌸 SYNOPSIS 🌸

int apparmor_uring_sqpoll (void );

there she is. one function, zero drama, returns an int. periodt ✨


πŸ’– ARGUMENTS πŸ’–

  • void β€” no arguments. literally none. nothing. the function said "i need nobody" and honestly? main character energy πŸ‘‘

🧚 DESCRIPTION 🧚

so what does it actually do, you ask? it checks to see if the current task is allowed to create a new io_uring kernel polling thread πŸŒ€

that's it, that's the whole thing. it's a permission check, bestie. it looks at whoever's asking, goes "hmm, and does this task get to spin up a fresh io_uring kernel polling thread?", and that's the entire personality. no cap 🫢


πŸ”₯ SEE ALSO πŸ”₯

the kernel file ./security/apparmor/lsm.c is where the lore lives, and here's the whole friend group it wants you to meet:

go read those too, they're all slaying in their own way πŸ’œ


that's the whole page, babe β€” no hidden lore, no warning section, no exit-status tea. just a clean little permission check and its very long list of mutuals. πŸ’€

and that's a wrap on this one, cuties πŸŽ€ brought to you by the ./security/apparmor source, dated October 2026, and filed under apparmor_uring_sqpoll(9) β€” catch you in the next manpage, mwah πŸ«Άβœ¨πŸ’–

πŸ“¦ where this page comes from