tipc_rcv(9)

okay bestie, you opened the Kernel API Manual and landed on tipc_rcv(9) — honestly? Short page, big main character energy 🫶 let me walk you through it, no cap.

---

✨ NAME ✨

tipc_rcv — the function that processes TIPC packets/messages arriving from off-node 💌 like, packets showing up from outside this node. iykyk 🌈

---

🌸 SYNOPSIS 🌸

void tipc_rcv (struct net *net , struct sk_buff *skb , struct
tipc_bearer *b );

---

🎀 ARGUMENTS 🎀

• net — the applicable net namespace 🌐 the one this whole thing belongs to, bestie
• skb — TIPC packet 📦 literally just the packet, that's it, that's the argument
• b — pointer to bearer message arrived on 🛣️ the bearer the message came in on

---

💜 DESCRIPTION 💜

So here's the vibe: tipc_rcv gets invoked with no locks held 🔓 not a single lock, periodt.

The bearer pointer, though — that one's serious. It must point to a valid bearer structure, which means it cannot be NULL 😤 no exceptions, bestie. But here's the little plot twist: the bearer can be inactive ✅ valid isn't the same as active, and that's the whole flex of this page.

⚠️ quick vibe check so you don't fumble it: b cannot be NULL, but it totally can be inactive. Two separate things, do not merge them 🙈

---

🦋 SEE ALSO 🦋

Kernel file ./net/tipc/node.c — and its entire friend group came out for this one 🔥

• struct tipc_node(9)
• tipc_node_crypto_rx(9)
• __tipc_node_link_up(9)
• tipc_node_link_up(9)
• tipc_node_link_failover(9)
• __tipc_node_link_down(9)
• tipc_node_get_linkname(9)
• tipc_node_xmit(9)
• tipc_node_bc_rcv(9)
• tipc_node_check_state(9)
• tipc_node_dump(9)

---

and that's the page, bestie 🎀 mwah 💋 — sourced straight from ./net/tipc, dated October 2026, filed under tipc_rcv(9) 💖✨ slay