crypto_final...hash_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 crypto_finalize_hash_request — like, the Kernel API Manual, section 9, bestie

okay so picture this: we're deep in the kernel, section 9 of the Kernel API Manual, and the function is literally called crypto_finalize_hash_request ✨ she's the one who wraps things up, no cap.

🎀 NAME 🎀

crypto_finalize_hash_request — the girl who finalizes one ahash_request if the request is done. that's it, that's the whole job. she closes the tab when the tab is actually closed 🫶

✨ SYNOPSIS ✨

void crypto_finalize_hash_request(struct crypto_engine *engine,
                                  struct ahash_request *req,
                                  int err);

returns void, so like. no return value. she gives you nothing back and honestly? iconic 💅

🌸 ARGUMENTS 🌸

  • engine — the hardware engine. yes, THE engine. her whole world revolves around this parameter 🔥
  • req — the request that needs to be finalized. the one being wrapped up. main character energy, fr fr 🎀
  • err — error number. that's it. an error number. if something went sideways, this is where it lives 😭

🦋 SEE ALSO 🦋

bestie, this is the group chat and everyone's in it, so let me introduce the whole crew 💖

Kernel file ./crypto/crypto_engine.c:

like, the transfer girks AND the finalize girks AND the engine girks all in one server. iykyk 🌈

no warnings, no bugs, no exit statuses on this one — she's a clean void, periodt. but do keep your crypto_finalize_request(9) links handy, that's the whole point of the SEE ALSO list 👑

kisses from the ./crypto directory 🍓 this page was written in October 2026 and yes, the header really does abbreviate her name to crypto_final...hash_request(9) — we don't know why, we just support her 💜

📦 where this page comes from