sk_wait_data(9)

💤 sk_wait_data(9) — the kernel API manual, bestie edition 💤

okay so bestie, welcome to sk_wait_data(9), straight out of the Kernel API Manual. this is the little guy that sits there and waits for data to show up at sk_receive_queue. it's giving patient main character energy fr fr 🎀

---

🌸 NAME 🌸

sk_wait_data — wait for data to arrive at sk_receive_queue ✨

---

🦋 SYNOPSIS 🦋

int sk_wait_data (struct sock *sk , long *timeo , const struct sk_buff
*skb );

like, exactly that, no cap. copy it character for character, the kernel does NOT do typos 💅

---

💖 ARGUMENTS 💖

• sk — the sock to wait on 🛌 this is the one doing the waiting, okay?
• timeo — for how long ⏳ yes queen, tell it your patience level
• skb — the last skb seen on sk_receive_queue 👀 the most recent one you clocked on the queue

---

🔥 DESCRIPTION 🔥

so here's the tea 🍵 — now socket state, including sk->sk_err, is changed only under lock, hence we may omit checks after joining the wait queue. like, the locking situation is handled, so we don't gotta double-check after we join. slay.

and we check the receive queue before schedule only as an optimization ✨ it is very likely that release_sock added new data, so like… we peek first because chances are there's already something there. lowkey smart, highkey iconic 🧚

ngl bestie, do NOT go adding extra checks thinking you're helping — the whole point is that the state is only touched under lock, so the post-join-queue checks just aren't needed 🙈

---

👑 SEE ALSO 👑

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

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

go read them all, iykyk 💜

---

mwah 💋 this page lives in ./net/core and it's dated October 2026 — that's the version/date flex, periodt. now go wait for your data like a good little socket 🫶