unlock_sock_fast(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… unlock_sock_fast β€” it's literally in the name, bestie

okay so welcome to the Kernel API Manual ✨ section 9 ✨, where we're talking about unlock_sock_fast β€” the iconic, unmatched, main character complement of lock_sock_fast. you locked it fast, now you unlock it. symmetry, periodt. πŸŽ€


🌸 NAME 🌸

unlock_sock_fast β€” the complement of lock_sock_fast

like... that's the whole vibe. they're a matching set. πŸ’–


✨ SYNOPSIS ✨

void unlock_sock_fast (struct sock *sk , bool slow );

returns nothing (void), takes two things. that's it. that's the function. slay. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sk β€” the socket. the actual socket. our girl. πŸ’œ
  • slow β€” slow mode. yeah, it's a bool, and yeah, it matters (see below πŸ‘€).

πŸ”₯ DESCRIPTION πŸ”₯

so this is the fast unlock socket for user context. 🧚

here's the tea: if slow mode is on, we call the regular release_sock. that's it β€” that's the branch. slow = true and you're taking the regular path, no cap.

lowkey the whole point here: fast unlock is the fast path, but "slow mode" being enabled means it hands off to the normal, regular release_sock instead. so don't forget to pass that flag correctly, bestie β€” it's literally the difference between the two paths. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, in the original order, no skipping (i would never):


and that's the page, bestie πŸ’…βœ¨ go forth and unlock responsibly πŸ“

signed, sealed, delivered from ./include/net 🌈 β€” dated October 2026 πŸŽ€, and yes, this is unlock_sock_fast(9) the whole way through, iykyk πŸ’–

πŸ“¦ where this page comes from