tipc_aead_clone(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tipc_aead_clone(9) β€” like, the TIPC AEAD key clone page, bestie

okay so this is a page from the Kernel API Manual, and it's literally all about tipc_aead_clone β€” cloning a TIPC AEAD key. yes bestie, we're in kernel land now, put your hair up πŸŽ€


✨ NAME ✨

tipc_aead_clone β€” Clone a TIPC AEAD key πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

int tipc_aead_clone (struct tipc_aead **dst , struct tipc_aead *src );

that's the whole vibe. two pointers, one function, zero drama (well… mostly, see the NOTE below πŸ‘€).


🌸 ARGUMENTS 🌸

  • dst β€” the dest key, aka where the cloning lands. this is the struct tipc_aead ** β€” a pointer to a pointer, main character energy fr fr πŸ’…
  • src β€” the source key you're cloning from. the original. the blueprint. the mother. πŸ‘‘

🫢 DESCRIPTION 🫢

okay so what this does is make a "copy" of the source AEAD key data over to the dest β€” and yes, "copy" is in quotes in the original for a reason, iykyk πŸ‘€.

here's the tea: the TFMs list is common for the keys β€” like, shared, not duplicated. so dest and src are lowkey sharing that list, no cap.

and because of that sharing situation, a reference to the source gets held in the "cloned" pointer, so later on when it's time to free stuff, everyone knows who's who. it's giving responsible memory management, honestly 🌈.


πŸ™ˆ NOTE πŸ™ˆ

this must be done in cluster-key mode only! no exceptions, bestie. if you're not in cluster-key mode, just… don't. πŸ’€

⭐ RETURN ⭐

0 in case of success β€” slay ✨

otherwise < 0 β€” not slay 😭


πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, honestly. kernel file ./net/tipc/crypto.c plus all of these icons:


and that's the page, bestie πŸ§šπŸ’œ

this lil masterpiece lives over in ./net/tipc, and it's dated October 2026 β€” future vibes only ⏳✨. the manual itself is tipc_aead_clone(9), mwah, bye πŸ“

πŸ“¦ where this page comes from