tipc_crypto_xmit(9)

📦 version 7.3.1, in nixpkgs unstable

💖 tipc_crypto_xmit — the kernel API glow-up 🎀

okay so bestie, welcome to tipc_crypto_xmit(9), from the Kernel API Manual. this is the function that builds and encrypts a TIPC message so it can go out into the world. it's giving "getting dressed before the party" energy, but for packets. 💅

✨ SYNOPSIS ✨

int tipc_crypto_xmit (struct net *net , struct sk_buff **skb , struct
tipc_bearer *b , struct tipc_media_addr *dst , struct tipc_node *__dnode
);

that's the whole signature, no cap. 🫶

🌸 ARGUMENTS 🌸

  • net — a struct net. yes. that's the whole description. iconic minimalism honestly. 👑
  • skb — the input/output message skb pointer. it goes in, and (spoiler) it comes back out either encrypted or gone.
  • b — the bearer used for xmit later. think of it as the ride this message is gonna catch. 🚗
  • dst — the destination media address. where it's headed. 📍
  • __dnode — the destination node for reference, if any. so like, if any — it's optional, she's flexible. 🦋

💫 DESCRIPTION 💫

so here's the tea, bestie. first, it builds an encryption message header on the top of the message. then it encrypts the original TIPC message by using the pending, master or active key — in that preference order, exactly, don't reorder them, that's the whole vibe check. 🔥

if the encryption is successful, the encrypted skb is returned directly or via the callback (depending on how it went down, iykyk). otherwise — and this is the dramatic part — the skb is freed! 💀 literally that's it, it's gone, she did not survive.

⚠️ ngl this is the one to remember: fail case = skb freed. no refunds, no returns. 😭

⭐ RETURN ⭐

here's what the return value is serving, one by one:

  • 0 — the encryption has succeeded (or no encryption happened at all). slay 🎉
  • -EINPROGRESS/-EBUSY — the encryption is ongoing, and a callback will be made. she's still getting ready, hang tight. ⏳
  • -ENOKEK — the encryption has failed due to no key. no key, no entry. 🔑❌
  • -EKEYREVOKED — the encryption has failed due to key revoked. that key lost its privileges bestie. 💀
  • -ENOMEM — the encryption has failed due to no memory. the budget said no. 😭
  • < 0 — the encryption has failed due to other reasons. the catch-all, the mystery, the ✨etcetera✨.

🔮 SEE ALSO 🔮

the whole friend group, fr fr — and they all live in the kernel file ./net/tipc/crypto.c:

and that's the whole page!! this one's filed under ./net/tipc, dated October 2026, and it's gonna show up in your searches as tipc_crypto_xmit(9) forever and ever. mwah 💋 go encrypt something gorgeous bestie 🧚💜

📦 where this page comes from