crypto_ahash_export_core(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– crypto_ahash_export_core β€” extract core state for message digest πŸ’–

Okay so bestie, welcome to the crypto_ahash_export_core(9) page β€” it's a Kernel API Manual moment and honestly? Iconic. Pull up a chair, we're talking about hash state and you're gonna get it, I promise. 🫢


✨ SYNOPSIS ✨

int crypto_ahash_export_core (struct ahash_request *req , void *out );

Yeah she's tiny, she's cute, she takes exactly two things. Let's meet them. πŸŽ€


🌸 ARGUMENTS 🌸

  • req β€” a reference to the ahash_request handle whose state is getting exported. Like, this is the request we're yoinking the state from, iykyk. πŸ’…
  • out β€” your output buffer. And not just any buffer β€” it has to be of sufficient size that it can hold the hash state. Do not skimp on the buffer, bestie, that's not the vibe. πŸ¦‹

πŸ’œ DESCRIPTION πŸ’œ

So what does it actually do? It exports the hash state without the partial block buffer. That's the whole thing. The core state gets pulled out, the partial block buffer stays home. No cap. ✨


πŸ”₯ CONTEXT πŸ”₯

Where can you call this? Softirq or process context. Both work, she's flexible. πŸ‘‘


⭐ RETURN ⭐

  • 0 β€” the export creation was successful, slay, we ate. πŸ“
  • < 0 β€” an error occurred, and honestly 😭 that's the sad path.

πŸ¦‹ SEE ALSO πŸ¦‹


🌟 Reminder for the group chat: out needs to be big enough to hold the hash state. That's the one thing that'll ruin your day if you forget it. πŸ’€

Okay that's the page! This one's from ./include/crypto/internal, dated October 2026, and it's the Kernel API Manual β€” crypto_ahash_export_core(9), periodt. πŸ’–πŸ‘‘

πŸ“¦ where this page comes from