cnstr_shdsc_...cipher_encap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 cnstr_shdsc_xts_skcipher_encap(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” yes, that's the manual name, we're fancy here πŸ’… β€” and today's main character is a little function called cnstr_shdsc_xts_skcipher_encap. Say it with me. I know. It's a mouthful. We love her anyway 🫢


✨ NAME ✨

cnstr_shdsc_xts_skcipher_encap β€” literally the xts skcipher encapsulation shared descriptor builder. That's her job. That's what she does. no cap πŸŽ€


πŸ’– SYNOPSIS πŸ’–

void cnstr_shdsc_xts_skcipher_encap (u32 * const desc , struct alginfo
*cdata );

look at that signature. flawless. iconic. she takes two pointers and returns absolutely nothing, which is honestly a whole mood 😭


πŸ¦‹ ARGUMENTS πŸ¦‹

  • desc β€” pointer to the buffer used for descriptor construction. think of it as the little construction site where the descriptor gets built, and she's the project manager πŸ—οΈ
  • cdata β€” pointer to block cipher transform definitions. and here's the tea: the valid algorithm values are OP_ALG_ALGSEL_AES ANDed with OP_ALG_AAI_XTS. that's the combo, that's the vibe check, don't try anything else ✨

πŸ”₯ SEE ALSO πŸ”₯

the whole group chat is here, and honestly they're all kind of famous:

like, the whole squad. encap AND decap versions. balanced, as all things should be βš–οΈβœ¨


heads up bestie: cnstr_shdsc_xts_skcipher_encap doesn't do encryption by itself, she just builds the descriptor. don't @ me, that's literally what the page says 🫢

and that's the page!! πŸ’œ it lives in ./drivers/crypto/caam, it's dated October 2026, and the header/footer energy is all cnstr_shdsc_...cipher_encap(9) β€” go off, kernel docs, you ate πŸŒˆβ­πŸ“

πŸ“¦ where this page comes from