ovpn_aead_crypto_req_sg(9)
β¨ ovpn_aead_crypto_req_sg β¨
Okay bestie, welcome to the ovpn_aead_crypto_req_sg(9) page β it's a kernel API manual situation and honestly it's a little niche but we're gonna slay it together π
πΈ NAME πΈ
ovpn_aead_crypto_req_sg β bestie, this one locates the scatterlist that sits right after the AEAD request inside a temporary buffer, and that buffer is the one you allocated using ovpn_aead_crypto_tmp_size. That's the whole vibe β¨
π¦ SYNOPSIS π¦
struct scatterlist * ovpn_aead_crypto_req_sg (struct crypto_aead *aead ,
struct aead_request *req );
π ARGUMENTS π
aeadβ the AEAD cipher handle, iconic, essential, the main character π₯reqβ a pointer to the AEAD request structure, and it lives in the temporary buffer, no cap π«Ά
π DESCRIPTION π
So like, here's the tea β: this function computes the starting address of the scatterlist β and that scatterlist is allocated immediately after the AEAD request structure. Like, right after. Adjacent. Besties in memory π₯°
And it aligns the pointer based on whatever the alignment requirements of the scatterlist structure are, because of course scatterlist has standards π
β RETURN β
It returns a pointer to the scatterlist. That's it, that's the gift π
π SEE ALSO π
- Kernel file
./drivers/net/ovpn/crypto_aead.cπ ovpn_aead_crypto_tmp_size(9)ovpn_aead_crypto_tmp_iv(9)ovpn_aead_crypto_tmp_req(9)
ngl bestie, go read those three siblings above before you start vibing with pointers in a temp buffer, iykyk π
β¨ ok that's the whole page, mwah π β¨
This little love letter lives under ./drivers/net/ovpn, dated October 2026 β stay hydrated, read your manpages, and remember: alignment is self-care π§ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms