crypto_shash_export(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie πŸ’– this is crypto_shash_export(9) from the Kernel API Manual, and it’s literally here to extract operational state for message digest. slay.

✨ SYNOPSIS ✨

int crypto_shash_export (struct shash_desc *desc , void *out );

🌸 ARGUMENTS 🌸

  • desc β€” reference to the operational state handle whose state is exported. like, the handle you’re grabbing the state from 🫢
  • out β€” output buffer of sufficient size that can hold the hash state. no tiny-buffer energy, okay? 😭

πŸ’– DESCRIPTION πŸ’–

So this function exports the hash state of the operational state handle into the caller-allocated output buffer out, which must have sufficient size β€” e.g. by calling crypto_shash_descsize. That’s the whole vibe: grab the state, put it in out, make sure out is big enough πŸ’…

bestie, the size part is not a suggestion. out must have sufficient size, and crypto_shash_descsize is the example the page gives for getting it. periodt. πŸ’€

πŸ¦‹ CONTEXT πŸ¦‹

Call it in Softirq or process context. that’s it, that’s the context. ✨

⭐ RETURN ⭐

  • 0 if the export creation was successful πŸŽ‰
  • < 0 if an error occurred 😭

🌈 SEE ALSO 🌈

The whole squad, bestie β€” every single one is invited 🫢:


That’s the whole page, bestie 🫢 source file ./include/crypto, dated October 2026, and the page is crypto_shash_export(9) β€” byeee πŸ’…βœ¨

πŸ“¦ where this page comes from