__tipc_node_link_up(9)

Okay bestie, welcome to the Kernel API Manual page for __tipc_node_link_up(9) 💖✨ It’s giving “handle addition of link,” and it’s short, iconic, and very much a kernel-internals moment. 🫶

🌸 NAME 🌸

__tipc_node_link_up — handle addition of link 💅

✨ SYNOPSIS ✨

void __tipc_node_link_up (struct tipc_node *n , int bearer_id , struct sk_buff_head *xmitq );

No cap, that’s the whole signature. 🎀

🎀 ARGUMENTS 🎀

• n — target tipc_node 🎯
• bearer_id — id of the bearer 🪪
• xmitq — queue for messages to be xmited on. (Yes, “xmited” is the source spelling, bestie; I’m not fixing it.) 📬

🚨 Node lock must be held by caller, fr fr. Do not skip this.

The link becomes active (alone or shared) or standby, depending on its priority. That’s the whole priority-driven vibe check, and it’s literally the main character energy of this function. 👑

🦋 SEE ALSO 🦋

The whole friend group is here, so don’t leave anyone on read:

• Kernel file ./net/tipc/node.c 📁
• struct tipc_node(9)
• tipc_node_crypto_rx(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_rcv(9)
• tipc_node_dump(9)

Go read them, iykyk 💜

Mwah 💋 sign-off time: source/version ./net/tipc, date October 2026, title __tipc_node_link_up(9) — that’s the footer tea, and I’m obsessed. Periodt. 🎀🦋