crypto_ahash_final(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_ahash_final(9) β€” Kernel API Manual ✨

Hey bestie, welcome to the Kernel API Manual 🫢 this one's the page for crypto_ahash_final(9), and no cap it's a little cutie. It's the "okay we're done, give me the digest" moment of the async hash world. Let's get into it.


✨ NAME ✨

crypto_ahash_final β€” calculate message digest πŸŽ€

🌸 SYNOPSIS 🌸

int crypto_ahash_final (struct ahash_request *req );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • req β€” your reference to the ahash_request handle πŸ’œ and that handle is literally holding all the information needed to perform the cipher operation. main character energy fr.

πŸ’– DESCRIPTION πŸ’–

So here's the vibe check: this function finalizes the message digest operation, and it creates the message digest based on literally all the data that got added to the cipher handle 🌈.

Where does the digest go? It gets placed into the output buffer that's registered with the ahash_request handle. That's it, that's the whole glow-up. πŸ’…

πŸ”₯ RETURN πŸ”₯

  • 0 β€” slay πŸ’… the message digest was successfully calculated
  • -EINPROGRESS β€” the data got fed into hardware (DMA) or it's queued for later, so like… it's working on it, chill πŸ™ˆ
  • -EBUSY β€” the queue is full 😭 and the request should be resubmitted later
  • other < 0 β€” bestie something went wrong, an error occurred πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is long long, but every single one of these is iconic in its own right, so:


and that's the whole page, bestie ✨ mwah πŸ’‹ this little love letter lives in ./include/crypto, dated October 2026, and it's version-era crypto_ahash_final(9) β€” iykyk πŸ§šπŸ’œ

πŸ“¦ where this page comes from