sk_capable(9)

💖 sk_capable(9) 💖

okay bestie, welcome to the Kernel API Manual entry for sk_capable — she's short, she's sweet, she's a socket capability check, and honestly? iconic. ✨

---

🌸 NAME 🌸

sk_capable — Socket global capability test 🫶

---

🦋 SYNOPSIS 🦋

bool sk_capable (const struct sock *sk , int cap );

like literally that's it, that's the whole signature, no cap 💅

---

🎀 ARGUMENTS 🎀

• sk — the socket you're gonna use a capability on, or through, if you will. the main character socket, fr fr 💖
• cap — the global capability you want to use. that's the one we're checking for 👑

---

✨ DESCRIPTION ✨

so the vibe check here is a test ✅ — you're asking: did the opener of this socket already have this capability back when the socket was created? 🕰️ and does the current process have the capability cap in all user namespaces? 🌈

both of those need to be true, and if they are — slay, the test passes 💅✨

ngl, this is the "was it valid then, and is it valid now" double-check. two eras, one capability check. periodt. 💀

---

👑 SEE ALSO 👑

peep these, bestie — the whole friend group 🫶:

Kernel file ./net/core/sock.c plus:

• sk_ns_capable(9)
• sk_net_capable(9)
• sk_set_memalloc(9)
• sk_alloc(9)
• sk_clone(9)
• skb_page_frag_refill(9)
• sk_wait_data(9)
• __sk_mem_raise_allocated(9)
• __sk_mem_schedule(9)
• __sk_mem_reduce_allocated(9)
• __sk_mem_reclaim(9)

---

okay that's the whole page, go be capable 💜

and finally, the cute little sign-off: this one comes from ./net/core, dated October 2026, and she's filed under sk_capable(9) in the Kernel API Manual. bye bestie, mwah 😭🎀🌸