crypto_lskcipher_statesize(9)

✨ crypto_lskcipher_statesize(9) ✨

okay bestie, buckle up — this is a page straight out of the Kernel API Manual, and honestly it's a short one but it's important, so let's get into it 💅

---

🌸 NAME 🌸

crypto_lskcipher_statesize — obtain state size 🎀

---

🦋 SYNOPSIS 🦋

unsigned int crypto_lskcipher_statesize(struct crypto_lskcipher *tfm);

---

💖 ARGUMENTS 💖

• tfm — the cipher handle, aka your little crypto bestie that you're asking the question about 🫶

---

👑 DESCRIPTION 👑

so here's the tea ☕ — some algorithms literally cannot be chained with the IV alone. like, that's just not how they roll. they carry internal state with them, and if you want to process data incrementally (chunk by chunk, no cap), that state has to be replicated. 😭

and the way you find out how big that state is? literally this function. that's it. that's the whole vibe check. ✨

---

⭐ RETURN ⭐

the state size, in bytes 💀 (yes, bytes, not bits, don't come for me)

---

🌈 SEE ALSO 🌈

okay this list is long but we're not skipping a single one, periodt. all of these live in the Kernel file ./include/crypto/skcipher.h:

• struct skcipher_request(9)
• struct skcipher_alg(9)
• struct lskcipher_alg(9)
• Symmetric Key Cipher API(9)
• crypto_alloc_skcipher(9)
• crypto_alloc_lskcipher(9)
• crypto_free_skcipher(9)
• crypto_free_lskcipher(9)
• crypto_has_skcipher(9)
• crypto_skcipher_ivsize(9)
• crypto_lskcipher_ivsize(9)
• crypto_skcipher_blocksize(9)
• crypto_lskcipher_blocksize(9)
• crypto_skcipher_chunksize(9)
• crypto_lskcipher_chunksize(9)
• crypto_skcipher_statesize(9)
• crypto_skcipher_setkey(9)
• crypto_lskcipher_setkey(9)
• crypto_skcipher_reqtfm(9)
• crypto_skcipher_encrypt(9)
• crypto_skcipher_decrypt(9)
• crypto_skcipher_export(9)
• crypto_skcipher_import(9)
• crypto_lskcipher_encrypt(9)
• crypto_lskcipher_decrypt(9)
• Symmetric Key Cipher Request Handle(9)
• crypto_skcipher_reqsize(9)
• skcipher_request_set_tfm(9)
• skcipher_request_alloc(9)
• skcipher_request_free(9)
• skcipher_request_set_callback(9)
• skcipher_request_set_crypt(9)

---

💡 pro tip from your fave: if you're doing incremental processing and you forgot to ask for the state size first, that's a you problem and the algorithm is gonna be real mad about it 🙈

---

and that's the whole page, bestie — short, sweet, and serving exactly what it says on the tin 🍓 this gem lives in ./include/crypto, and it's dated October 2026, filed under crypto_lskcipher_statesize(9) 💜 mwah, go read the manpage, ily 🧚