akcipher_request_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ akcipher_request_alloc πŸ’…

okay so bestie, welcome to the Kernel API Manual entry for akcipher_request_alloc β€” yes that's the whole name, no it's not short, we don't make the rules πŸŽ€. This is the function that allocates a public key request for you. That's it. That's the vibe. Let me walk you through it 🫢


🌸 SYNOPSIS 🌸

struct akcipher_request * akcipher_request_alloc (struct crypto_akcipher
*tfm , gfp_t gfp );

literally the whole signature. look at her go ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • tfm β€” the AKCIPHER tfm handle, and no you can't just make one up, it has to be one you got from crypto_alloc_akcipher. gotta have the real thing, bestie πŸ’–
  • gfp β€” the allocation flags. yeah, the gfp_t flags, you know the ones. this is you telling the kernel how to behave while it's grabbing memory for you 🌈

πŸ‘‘ RETURN πŸ‘‘

So what do you get back? A freshly allocated handle in case of success πŸŽ‰ β€” or NULL in case of an error 😭. Nothing in between, no surprises, no hidden lore. Check for that NULL, queen. periodt.


πŸ’œ SEE ALSO πŸ’œ

okay this is the bestie section, so many icons in here, let me introduce everyone:

all of them. every single one. go read them, iykyk πŸ“šβœ¨


and that's the page!! sourced from ./include/crypto, dated October 2026 β€” mwah, bye bestie, go allocate responsibly πŸ’…πŸ”₯πŸŽ€

πŸ“¦ where this page comes from