sk_ns_capable(9)

hiii bestie 💖 welcome to sk_ns_capable(9) from the Kernel API Manual — it’s the general socket capability test and it’s giving “tiny function, serious permission vibes” ✨

🌸 NAME 🌸

sk_ns_capable — General socket capability test 💅

✨ SYNOPSIS ✨

bool sk_ns_capable (const struct sock *sk , struct user_namespace
       *user_ns , int cap );

🎀 ARGUMENTS 🎀

• sk — Socket to use a capability on or through. yes bestie, the socket itself 🧦
• user_ns — The user namespace of the capability to use. it’s the namespace context, no cap 🧢
• cap — The capability to use. the actual capability being checked 🔑

🦋 DESCRIPTION 🦋

okay so this one is a test 👀 it checks whether the opener of the socket had the capability when the socket was created, and whether the current process has the capability cap in the user namespace user_ns. it’s a two-part vibe check: opener-at-socket-creation time + current-process time, with cap in user_ns — both pieces are literally in the sentence, bestie 💀

💜 SEE ALSO 💜

• Kernel file: ./net/core/sock.c
• sk_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 bye bestie 🫶 this little page is from the Kernel API Manual, source ./net/core, dated October 2026 — mwah 💋