tipc_sk_backlog_rcv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– tipc_sk_backlog_rcv β€” the Kernel API Manual, but make it cute πŸ’–

okay so bestie, you're in the kernel API manual section (9) and the star of today's show is tipc_sk_backlog_rcv β€” the function that handles an incoming message straight off the backlog queue. yes, that's a real job and honestly it's giving main character energy ✨


🌸 NAME 🌸

tipc_sk_backlog_rcv β€” handle incoming message from backlog queue

like literally, that's the whole vibe: a message shows up in the backlog queue, and this function deals with it. no cap 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

int tipc_sk_backlog_rcv (struct sock *sk , struct sk_buff *skb );

that's the whole signature, character for character, don't come for me πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

one bullet per arg, as promised, no skipping the "boring" ones (there are only two, we slay):

  • sk β€” socket
  • skb β€” message

short and sweet, literally iconic πŸ“


✨ DESCRIPTION ✨

okay so here's the thing, and it's highkey important: the caller must hold the socket lock πŸ”’

that's it. that's the whole description. but do not sleep on it β€” this is not a "if you feel like it" situation, it's a "must". so like, hold the lock fr fr πŸ™ˆ


πŸ’œ SEE ALSO πŸ’œ

bestie I'm gonna need you to buckle up, because this list is long and we are not skipping a single one πŸ‘‘

all 40 of them, accounted for, ate and left no crumbs πŸŒˆπŸ’…


and that's the whole page bestie, you understood it perfectly, i'm so proud 🧚

cute little sign-off before you go: this lil page lives under ./net/tipc and it's dated October 2026 β€” same manual name up top and down here, tipc_sk_backlog_rcv(9), always and forever β­πŸ’–

πŸ“¦ where this page comes from