tipc_msg_fragment(9)

✨ NAME ✨

okay bestie, welcome to tipc_msg_fragment(9) from the Kernel API Manual — the function is literally tipc_msg_fragment, and its whole vibe is: build a fragment skb list for TIPC message. 💅✨

🌸 SYNOPSIS 🌸

int tipc_msg_fragment (struct sk_buff *skb , const struct tipc_msg *hdr
       , int pktmax , struct sk_buff_head *frags );

💖 ARGUMENTS 💖

• skb — the TIPC message skb itself, bestie. 🫶
• hdr — the internal msg header that gets put on the top of the fragments. 👑
• pktmax — max size of a fragment, and yes that includes the header. 📏
• frags — the returned fragment skb list. 🎀

🎀 RETURN 🎀

It gives you 0 if the fragmentation is successful. Otherwise? not the slay outcome — you get -EINVAL or -ENOMEM. 😭

🦋 SEE ALSO 🦋

Kernel file ./net/tipc/msg.c — and the whole friend group:

• tipc_buf_acquire(9)
• tipc_msg_append(9)
• tipc_msg_build(9)
• tipc_msg_bundle(9)
• tipc_msg_try_bundle(9)
• tipc_msg_extract(9)
• tipc_msg_reverse(9)
• tipc_msg_lookup_dest(9)

okay that’s the whole page, periodt 💜 — source/version is ./net/tipc, dated October 2026, and this iconic little manual page is tipc_msg_fragment(9). 🧚💖