tipc_sk_conn_proto_rcv(9)

📦 version 7.3.1, in nixpkgs unstable

💅 tipc_sk_conn_proto_rcv(9) ✨

okay so bestie, welcome to the Kernel API Manual page for tipc_sk_conn_proto_rcv(9) — yes the whole title, yes it's a mouthful, no we are not shortening it, it's giving main character energy and we respect it 🫶

This one's a function in the TIPC socket code and it handles exactly one job. Let's get into it 🌸

✨ NAME ✨

tipc_sk_conn_proto_rcv — literally just: receive a connection mng protocol message 💌

no cap, that's the entire vibe. it receives. it's a connection mng protocol message. iconic.

🦋 SYNOPSIS 🦋

void tipc_sk_conn_proto_rcv (struct tipc_sock *tsk , struct sk_buff *skb
, struct sk_buff_head *inputq , struct sk_buff_head *xmitq );

note the void btw — this one doesn't hand you anything back, it just does the thing and dips 🙈

🎀 ARGUMENTS 🎀

four args, all of them matter, let's go through them one by one like we're doing a vibe check on each 💅

  • tsk — the receiving socket. this is the one getting the message, she's the main character here 👑
  • skb — pointer to message buffer. yeah it's a pointer, it's a buffer, it's the message, all of the above 🍓
  • inputq — buffer list containing the buffers. the whole little friend group of buffers 🧚
  • xmitq — output message area. this is where stuff goes out, different queue, different destiny 🌈
bestie pls don't mix up inputq and xmitq, they are literally named in and out for a reason 😭

⭐ SEE ALSO ⭐

okay this list is LONG long, like genuinely enormous, so buckle up — we're listing every single one because nobody gets left behind 💖

like I said. enormous. but we ate. periodt 🍽️

and that's the page!! mwah 💋 — this lil masterpiece lives in ./net/tipc and it's dated October 2026, so yeah, future-coded of it. go read some kernel source bestie, ily, bye 🎀✨💜

📦 where this page comes from