aead_request_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– aead_request_alloc(9) πŸ’–

okay so bestie, welcome to the aead_request_alloc page β€” it's from the Kernel API Manual and it's literally the glow-up moment where your request data structure gets born ✨


🌸 NAME 🌸

aead_request_alloc β€” allocate request data structure (yes that's the whole job, and she does it flawlessly πŸ’…)


πŸ¦‹ SYNOPSIS πŸ¦‹

struct aead_request * aead_request_alloc (struct crypto_aead *tfm ,
gfp_t gfp );

πŸŽ€ ARGUMENTS πŸŽ€

  • tfm β€” the cipher handle that gets registered with the request 🫢 like, she's the plus-one you're bringing to the party.
  • gfp β€” the memory allocation flag that's handed off to kmalloc by the API call. it's giving "pass the note along" energy ngl.

✨ DESCRIPTION ✨

So here's the vibe: this call allocates the request data structure that you must use with the AEAD encrypt and decrypt API calls. no substitutions, bestie, this is the one πŸ‘‘

And during the allocation, the aead handle you provided gets registered right into the request data structure. main character registration moment fr fr 🌟


🌈 RETURN 🌈

  • allocated request handle in case of success πŸ’–
  • or NULL if out of memory 😭 (the tragedy, the drama, the -ENOMEM of it all)

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/crypto/aead.h β€” Authenticated Encryption With Associated Data (AEAD) Cipher API(9), struct aead_request(9), struct aead_alg(9), crypto_alloc_aead(9), crypto_free_aead(9), crypto_has_aead(9), crypto_aead_ivsize(9), crypto_aead_authsize(9), crypto_aead_blocksize(9), crypto_aead_setkey(9), crypto_aead_setauthsize(9), crypto_aead_encrypt(9), crypto_aead_decrypt(9), Asynchronous AEAD Request Handle(9), crypto_aead_reqsize(9), aead_request_set_tfm(9), aead_request_free(9), aead_request_set_callback(9), aead_request_set_crypt(9), aead_request_set_ad(9)

like, that's the whole friend group and they're all iconic in their own way πŸ§šπŸ’œ


and that's the page, bestie!! πŸ“ tysm for reading, mwah πŸ’‹

sign-off szn: this beauty lives in ./include/crypto, dated October 2026, and it's the aead_request_alloc(9) era obviously πŸ’…βœ¨ see u in the kernel, xoxo πŸ¦‹

πŸ“¦ where this page comes from