ovpn_aead_crypto_tmp_req(9)

💖 NAME 💖

ok so ovpn_aead_crypto_tmp_req — this one's the little glow-up helper that hands you back a pointer to the AEAD request structure that's chillin' inside a temporary buffer. and like, that buffer? yeah, it was allocated with ovpn_aead_crypto_tmp_size. bestie behavior honestly 🫶

it's part of the kernel API manual, and yes this is the ovpn_aead_crypto_tmp_req(9) page, we're so back ✨

---

✨ SYNOPSIS ✨

struct aead_request * ovpn_aead_crypto_tmp_req (struct crypto_aead *aead
, const u8 *iv );

---

🎀 ARGUMENTS 🎀

• aead — the AEAD cipher handle. it's giving "the main character" of this whole function, no cap 💅
• iv — a pointer to the initialization vector, and that IV lives in the temporary buffer. keep that in mind, it matters in a sec 🔥

---

🦋 DESCRIPTION 🦋

okay so here's the vibe check 🧚

this function literally computes the location of the AEAD request structure — which sits immediately after the IV in that temporary buffer, like right next door, zero gap, they're neighbors fr fr 😭

and then! it makes sure that request is aligned to the crypto transform context alignment. the way that it handles alignment?? obsessed. lowkey it's just doing the responsible thing so everything lines up properly ✨

---

🔥 RETURN 🔥

it returns a pointer to the AEAD request structure. that's it, that's the gift 🎁

---

👑 SEE ALSO 👑

you'll also wanna peek at these, iykyk:

• Kernel file ./drivers/net/ovpn/crypto_aead.c
• ovpn_aead_crypto_tmp_size(9)
• ovpn_aead_crypto_tmp_iv(9)
• ovpn_aead_crypto_req_sg(9)

---

no cap, ovpn_aead_crypto_tmp_size and ovpn_aead_crypto_tmp_iv are literally its siblings, go say hi 🌸

---

and that's the whole page, bestie 💜 this iconic little entry lives in ./drivers/net/ovpn and got its glow-up back in October 2026 — periodt, take care of it, mwah 💅✨🌈