crypto_final...pher_request(9)

💅 NAME

okay so bestie, gather round — this is crypto_finalize_skcipher_request(9) from the Kernel API Manual, section 9, and it does exactly one job: it finalizes one skcipher_request if the request is done. that's it. that's the whole vibe. 🎀

✨ SYNOPSIS ✨

void crypto_finalize_skcipher_request (struct crypto_engine *engine ,
struct skcipher_request *req , int err );

like, literally the entire signature. no cap. 🫶

🦋 ARGUMENTS 🦋

• engine — the hardware engine 💖 (yes queen, the actual silicon doing the work)
• req — the request need to be finalized 👑 (it's giving "this one's done, wrap it up")
• err — the error number 🌸 (so it knows whether to celebrate or send condolences)

🌈 SEE ALSO 🌈

so here's the whole friend group, and honestly? they ate. 🔥

Kernel file ./crypto/crypto_engine.c:

• crypto_finalize_request(9)
• crypto_pump_requests(9)
• crypto_transfer_request(9)
• crypto_transfer_request_to_engine(9)
• crypto_transfer_aead_request_to_engine(9)
• crypto_transfer_akcipher_request_to_engine(9)
• crypto_transfer_hash_request_to_engine(9)
• crypto_transfer_kpp_request_to_engine(9)
• crypto_transfer_skcipher_request_to_engine(9)
• crypto_finalize_aead_request(9)
• crypto_finalize_akcipher_request(9)
• crypto_finalize_hash_request(9)
• crypto_finalize_kpp_request(9)
• crypto_engine_start(9)
• crypto_engine_stop(9)
• crypto_engine_alloc_init_and_set(9)
• crypto_engine_alloc_init(9)
• crypto_engine_exit(9)

ngl bestie, this page is short but it's iconic in a lowkey way — one function, three arguments, and a whole ecosystem of crypto_engine friends waiting in SEE ALSO. go read them too, iykyk. 💀💜

and that's the tea 🍓 — this page lives in ./crypto, dated October 2026, and the footer's whole moment is crypto_final...pher_request(9). slay, bye ✨🧚‍♀️