crypto_finalize_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 crypto_finalize_request(9) — your fave lil' "we're done here" function, from the Kernel API Manual ✨

okay so picture this: you're deep in the kernel, the crypto engine is doing its whole thing, and a request has officially finished its main character arc. bestie, that's where this function walks in 🎀

🌸 NAME 🌸

crypto_finalize_request — finalize one request if the request is done 💖

like, if the request is done. that's the whole vibe check. no cap.

✨ SYNOPSIS ✨

void crypto_finalize_request (struct crypto_engine *engine , struct crypto_async_request *req , int err );

it returns void, which honestly is so chill of it — nothing to hand back, it just does the thing 🫶

🦋 ARGUMENTS 🦋

  • engine — the hardware engine 💀 the actual physical-ish machinery doing the crypto. your main character.
  • req — the request need to be finalized 🎀 yep, the one that's gotta get wrapped up. that request. right there.
  • err — error number 😭 so if something went sideways, this is where you say so. it's an error number, bestie. numbers. errors. you know the drill.

👑 SEE ALSO 👑

okay so the whole friend group, and yes we're naming everyone, no cap, nobody gets left out of the group chat 🫶

Kernel file ./crypto/crypto_engine.c — the source, the origin story, the place it all lives ✨

the transfer-to-engine squad 💅

the finalize family — literally this function's siblings 🧚

the engine lifecycle icons ⭐

aaaand that's the page, bestie 🌈 one last thing before you go — this whole thing lives in ./crypto and the version-date stamp on it is October 2026, so like, future vibes, iykyk. slay, bye 💜🌸

📦 where this page comes from