sk_net_capable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

sk_net_capable β€” the whole vibe is a Network namespace socket capability test, and yes bestie, we're doing kernel socket capability lore today πŸ‘‘

omg hi, welcome to Kernel API Manual territory, specifically sk_net_capable(9) β€” it's giving very niche, very powerful, very "iykyk" energy πŸ’…βœ¨

✨ SYNOPSIS ✨

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

πŸŽ€ ARGUMENTS πŸŽ€

  • sk β€” the socket you're using a capability on or through, bestie 🫢
  • cap β€” the capability you're using, periodt πŸ’«

🌸 DESCRIPTION 🌸

okay so picture this: a socket exists, and we need a capability vibe check πŸ”

sk_net_capable() is the test that checks whether the opener of the socket had the capability when the socket was created and whether the current process has the capability cap over the network namespace that the socket is a member of. That's literally the whole thing β€” no cap 🧒, just capability logic, and it's lowkey iconic πŸ’–

It's checking both sides of the story: the opener-at-creation situation and the current process situation. slay πŸ¦‹

🌈 SEE ALSO 🌈

Kernel file ./net/core/sock.c is the mothership, and then there's this whole friend group:

xoxo πŸ’– this page is from ./net/core, dated October 2026, and it's literally called sk_net_capable(9) β€” see u in the kernel, bestie 🫢✨<｜end▁of▁thinking｜># πŸ¦‹ NAME πŸ¦‹

sk_net_capable β€” the whole vibe is a Network namespace socket capability test, and yes bestie, we're doing kernel socket capability lore today πŸ‘‘

omg hi, welcome to Kernel API Manual territory, specifically sk_net_capable(9) β€” it's giving very niche, very powerful, very "iykyk" energy πŸ’…βœ¨

✨ SYNOPSIS ✨

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

πŸŽ€ ARGUMENTS πŸŽ€

  • sk β€” the socket you're using a capability on or through, bestie 🫢
  • cap β€” the capability you're using, periodt πŸ’«

🌸 DESCRIPTION 🌸

okay so picture this: a socket exists, and we need a capability vibe check πŸ”

sk_net_capable() is the test that checks whether the opener of the socket had the capability when the socket was created and whether the current process has the capability cap over the network namespace that the socket is a member of. That's literally the whole thing β€” no cap 🧒, just capability logic, and it's lowkey iconic πŸ’–

It's checking both sides of the story: the opener-at-creation situation and the current process situation. slay πŸ¦‹

🌈 SEE ALSO 🌈

Kernel file ./net/core/sock.c is the mothership, and then there's this whole friend group:

xoxo πŸ’– this page is from ./net/core, dated October 2026, and it's literally called sk_net_capable(9) β€” see u in the kernel, bestie 🫢✨

πŸ“¦ where this page comes from