kpp_request_alloc(9)

💅 kpp_request_alloc 💅

okay bestie, so this is a page from the Kernel API Manual — section 9 — and it's all about one lil function: kpp_request_alloc. literally the glow-up moment where a KPP request gets its very own memory. no cap, it's giving "birth certificate for a request object" 🎀

---

✨ NAME ✨

kpp_request_alloc — allocates kpp request 🦋

like... that's it. that's the whole job. it allocates a kpp request. iconic, honestly 👑

---

🌸 SYNOPSIS 🌸

struct kpp_request * kpp_request_alloc (struct crypto_kpp *tfm , gfp_t
       gfp );

---

💖 ARGUMENTS 💖

• tfm — the KPP tfm handle, bestie. and not just any handle — it's the one you allocated with crypto_alloc_kpp. please don't show up with a random one, that's not the vibe 🙈
• gfp — the allocation flags. yep, the classic gfp situation. it's giving "how hard should the kernel try" energy ✨

---

⭐ RETURN ⭐

ok so here's the tea ☕ — on success you get the allocated handle back. slay! but if something goes sideways and there's an error? you get NULL. no handle, no vibes, just NULL 😭 fr fr check for it.

---

🦋 SEE ALSO 🦋

the whole friend group, gathered for you 🫶 — and yes, they're referencing the kernel file ./include/crypto/kpp.h:

• struct kpp_request(9)
• struct crypto_kpp(9)
• struct kpp_alg(9)
• Generic Key-agreement Protocol Primitives API(9)
• crypto_alloc_kpp(9)
• crypto_free_kpp(9)
• kpp_request_free(9)
• kpp_request_set_callback(9)
• kpp_request_set_input(9)
• kpp_request_set_output(9)
• struct kpp_secret(9)
• crypto_kpp_set_secret(9)
• crypto_kpp_generate_public_key(9)
• crypto_kpp_compute_shared_secret(9)
• crypto_kpp_maxsize(9)

---

💀 reminder bestie: NULL is a real possible outcome here, not a personality trait. handle it.

---

ok that's the page!! sourced straight from ./include/crypto, dated October 2026 — mwah, go allocate something cute 💜🧚‍♀️