aes_xts_encrypt(9)

💅 aes_xts_encrypt(9) — like, the Kernel API Manual, bestie ✨

okay so real talk: this one lives in the Kernel API Manual and it's called aes_xts_encrypt. Obsessed already. It does exactly one thing and does it gorgeously: it encrypts your data with AES-XTS. That's the whole vibe. 🎀

---

✨ SYNOPSIS ✨

void aes_xts_encrypt (u8 *dst , const u8 *src , size_t len , u8 tweak[static AES_BLOCK_SIZE] , const struct aes_xts_key *key , bool cont );

Like… look at her. Six params, zero drama. 💅

---

🌸 ARGUMENTS 🌸

• dst — the destination buffer, aka where the encrypted goodness goes. She's flexible: in-place or out-of-place, both iconic, both valid. Any other kind of overlap? behavior is unspecified — no cap, don't do it. 🙈
• src — the source data, your raw lil plaintext (or whatever you're feeding her). 🍓
• len — how many bytes to encrypt. Important rules here, bestie, write these down: on non-final calls it must be a nonzero multiple of AES_BLOCK_SIZE. On the final call it can be any value >= AES_BLOCK_SIZE — which literally means ciphertext stealing is supported. she ate. 🔥
• tweak — the tweak, duh. She gets updated with the next value… unless len isn't a multiple of AES_BLOCK_SIZE, in which case the value is unspecified. so like, don't go reading her after that, mwah. 💀
• key — the key 💜 — and NOT just any key, it's gotta be one already prepared with aes_xts_preparekey. Do the prep first. main character energy requires setup.
• cont — the continuation flag, the plot device of this whole function:
  • false → begin encrypting a new message (this is when she does the tweak encryption) 🫶
  • true → continue encrypting a message (and she skips the tweak encryption) ⭐

---

🦋 DESCRIPTION 🦋

So she supports both one-shot and incremental encryption, which is genuinely so versatile of her.

The recipe, step by step:

1. On the first call, pass cont = false. 🎀
2. On any later calls, pass cont = true and the updated tweak. ✨

And like, small but crucial detail: all earlier len must have been multiples of AES_BLOCK_SIZE. That's the rule, iykyk. 💅

---

🌈 CONTEXT 🌈

Any context. Literally any. She doesn't care where you call her from, she's chill like that. 😌

---

💖 SEE ALSO 💖

• Kernel file ./include/crypto/aes-xts.h — the struct aes_xts_key(9) lives there, go say hi 👑
• aes_xts_preparekey(9) — do this BEFORE you call her, remember? 🔑
• aes_xts_decrypt(9) — the other direction, her sister fr fr 🧚

---

okay that's the whole page, and honestly?? flawless. this came from the <pink>./include/crypto</pink> corner of the kernel, dated October 2026, and it's page aes_xts_encrypt(9) — so go forth, encrypt responsibly, and don't overlap your buffers weirdly. 💜🦋✨