crypto_final...pher_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 crypto_finalize_akcipher_request(9) — the Kernel API Manual, section 9, bestie

Okay so picture this: you're deep in the kernel, you've got a whole hardware crypto engine, and somebody has to be the responsible one who says "bestie, this akcipher request? it's done. let it go." That somebody is this function. It lives in the Kernel API Manual, section 9, and honestly? It's giving cleanup crew main character energy. 🧹✨

🌸 NAME 🌸

crypto_finalize_akcipher_request — finalize one akcipher_request if the request is done

Like, if it's done. Read the if, bestie. 👀

✨ SYNOPSIS ✨

void crypto_finalize_akcipher_request(struct crypto_engine *engine,
                                      struct akcipher_request *req,
                                      int err);

No return value, because it's a void girlie and it simply doesn't owe you a status code. 💅

🎀 ARGUMENTS 🎀

  • engine — the hardware engine. The whole vibe. The machinery doing the actual work 🛠️
  • req — the request that needs to be finalized. Yes, that one. It's had a long day, let it rest 😭
  • err — the error number. Fr fr, pass along what happened 🫶

🦋 SEE ALSO 🦋

So many siblings, one big crypto engine family. Go say hi to all of them 👑:

Heads up bestie: some of the page header was looking a lil truncated in the wild (crypto_final...pher_request(9)), but the full name is crypto_finalize_akcipher_request — don't let the ellipsis gaslight you 💀

And that's the whole page, no cap 🌈 That was the Kernel API Manual, sourced from ./crypto, dated October 2026 — mwah, slay, go finalize some requests responsibly 💖🎀🦋

📦 where this page comes from