skcipher_request_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… skcipher_request_alloc(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so this is skcipher_request_alloc, straight out of the Kernel API Manual, and it's genuinely one of the first things you'll touch when you're doing symmetric key cipher stuff. it's giving "allocator era" ✨


✨ NAME ✨

skcipher_request_alloc β€” allocate request data structure πŸ¦‹


🌸 SYNOPSIS 🌸

struct skcipher_request * skcipher_request_alloc (struct crypto_skcipher
*tfm , gfp_t gfp );

πŸ’– ARGUMENTS πŸ’–

  • tfm β€” the cipher handle that's gonna get registered with the request 🫢 like, this is the crypto you're bringing to the party.
  • gfp β€” the memory allocation flag, which gets handed straight to kmalloc by the API call. basically the "how hard should I try to get memory" vibe check πŸ’€

πŸ‘‘ DESCRIPTION πŸ‘‘

Allocate the request data structure β€” the one you must use with the skcipher encrypt and decrypt API calls. no substitutions, no DIY-ing it, periodt.

During the allocation, the skcipher handle you passed in gets registered in the request data structure. so tfm goes in, request comes out, everything's linked up and iconic πŸ’…


⭐ RETURN ⭐

  • you get the allocated request handle back in case of success πŸŽ‰
  • or NULL if out of memory 😭 (yes, that's a real outcome, plan accordingly)

🌈 SEE ALSO 🌈

okay this list is a journey, so buckle up bestie β€” and don't skip it, it's lowkey the whole ecosystem:

that's right, the whole friend group 🫢 iykyk.


anyway, this page lives in ./include/crypto, dated October 2026, and that's the whole manual β€” mwah, go allocate something cute πŸ’‹πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from