SOCK_CONNECT_BIND(9)

✨ SOCK_CONNECT_BIND ✨

okay bestie, real talk — this is a page from the Kernel API Manual, section 9, and it's a tiny little icon, not a whole long chapter. So let's not waste a single second. 🎀

💖 NAME 💖

SOCK_CONNECT_BIND — the &sock->sk_userlocks flag that tells the kernel "bestie, auto-bind me at connect() time, kthx." 🌸

That's literally the whole thing, no cap. It's a flag, it lives in the sk_userlocks field of the sock, and its whole personality is bind automatically when connect happens. Periodt. 💅

🌈 SYNOPSIS 🌈

SOCK_CONNECT_BIND

yep. that's it. that's the synopsis. not me being dramatic, it's genuinely just the one token. lowkey iconic for how little it needs to say. ✨

🦋 SEE ALSO 🦋

okay this is the part with the actual homework — these are all in the kernel file ./include/net/sock.h, and the related pages are, in the original order (don't skip, I see you 👀):

• struct sock_common(9) — the common core bits shared around
• struct sock(9) — the sock struct itself, obviously
• sk_user_data_is_nocopy(9)
• __locked_read_sk_user_data_with_flags(9)
• __rcu_dereference_sk_user_data_with_flags(9)
• sk_for_each_entry_offset_rcu(9)
• lock_sock_fast(9)
• unlock_sock_fast(9) — the matching unlock, you know they come as a pair 💜
• sk_wmem_alloc_get(9)
• sk_rmem_alloc_get(9)
• sk_has_allocations(9)
• skwq_has_sleeper(9)
• sock_poll_wait(9)
• sk_page_frag(9)
• _sock_tx_timestamp(9)
• sk_eat_skb(9)

like, go read them if you want the full lore, they're all right there in ./include/net/sock.h. iykyk 🧚

fr fr though — this page is short because the flag is short. it's one bit of sk_userlocks doing one job. don't overthink it, just know it exists and it auto-binds at connect(). 🫶

and that's the whole vibe check 💀💖 — this one came out of ./include/net, dated October 2026, straight from the Kernel API Manual (section 9), and honestly? slay. stan a minimal manpage. 🌟 bye bestie!! 🍓👑