crypto_finalize_kpp_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 crypto_finalize_kpp_request(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're deep in the kernel, the crypto_engine girlies are all doing their thing, and a kpp_request just wrapped up. this function is the one that says "you're done, go home, we're finalizing you" ✨

🌸 NAME 🌸

crypto_finalize_kpp_request — finalizes one kpp_request if that request is, like, actually done ✅ no cap, that's literally the whole job.

💖 SYNOPSIS 💖

void crypto_finalize_kpp_request (struct crypto_engine *engine , struct
kpp_request *req , int err );

it returns void, so don't go looking for a return value, she gives you nothing back 🫶 (and honestly? iconic behavior.)

🦋 ARGUMENTS 🦋

  • engine — the hardware engine 💻 that's doing the actual work. this is the main character of the operation.
  • req — the request that needs to be finalized 🎀 like, the one that has to get its little ending.
  • err — the error number 😭 if something went sideways, this is where it lives. it's an int.

🔥 SEE ALSO 🔥

all the sister functions and friends-of-friends, so you can go down the whole rabbit hole 🐇💜 — and the kernel file itself, ./crypto/crypto_engine.c:

💀 real talk: that's a whole friend group of finalize and transfer functions. pick your fighter, they're all in ./crypto.

and that's the whole vibe check, bestie 🌈 this little icon came from the ./crypto directory, dated October 2026 — so mark your calendar and slay 🧚‍♀️💖 periodt.

📦 where this page comes from