crypto_final...aead_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 crypto_finalize_aead_request(9) — from the Kernel API Manual, bestie ✨

Okay so listen 👑 — this is the <purple>Kernel API Manual</purple> page for crypto_finalize_aead_request, and it's genuinely short and sweet, so we're gonna get through it together, no cap 🫶

✨ NAME ✨

crypto_finalize_aead_request — finalize one aead_request if the request is done 💖

That's literally it, that's the whole job. If it's done, you finalize it. Slay.

🌸 SYNOPSIS 🌸

void crypto_finalize_aead_request(struct crypto_engine *engine,
                                  struct aead_request *req,
                                  int err);

Returns void, so like… no return value to obsess over, she just does the thing and dips 💅

🎀 ARGUMENTS 🎀

  • engine — the hardware engine 🛠️ the actual crypto hardware squad doing the work.
  • req — the request that needs to be finalized 🌈 iykyk, she's the main character here.
  • err — the error number 💀 so everybody knows how it went.

🦋 SEE ALSO 🦋

The whole friend group 🫶 — all of these live in the kernel file ./crypto/crypto_engine.c:

Ngl bestie, this page has no warnings, no exit statuses, no env vars — just a tidy little function doing her little finalize moment. Respect it. 🎀

Okay that's the whole vibe check ✅ — this beauty comes from ./crypto, October 2026 edition, and honestly? Iconic of her. Bye bestie, go finalize those requests 💖✨🦋

📦 where this page comes from