STRUCT CRYPTO_KPP_SPAWN(9)

📦 version 7.3.1, in nixpkgs unstable

💅 struct crypto_kpp_spawn(9) — the kernel API manual, but make it make sense

Okay bestie, so this is a page from the Kernel API Manual, all about struct crypto_kpp_spawn. Yes the title is literally the same as the struct name, that's just how these pages roll, we move. 🎀

✨ NAME ✨

struct crypto_kpp_spawn — it's the KPP algorithm spawn. That's the whole name section, she's short and she knows it. 💅

🌸 SYNOPSIS 🌸

struct crypto_kpp_spawn {
    struct crypto_spawn base;
};

That's it, that's the whole struct. One member. Iconic minimalism, honestly. ✨

🦋 Members 🦋

  • base — this one is internal, so like… not your business, bestie, it's the crypto core's generic spawn state. Hands off, iykyk. 🙈

💖 Description 💖

So here's the vibe: template instances can get a hold on some inner KPP algorithm by binding a struct crypto_kpp_spawn via crypto_grab_kpp. That's step one, that's how you grab it. 🫶

Then, like, subsequently — later, after the grabbing has happened — transforms may get instantiated from the referenced inner struct kpp_alg by means of crypto_spawn_kpp. Grab first, spawn second. That's the whole pipeline, no cap. 🔥

🌈 SEE ALSO 🌈

Kernel file ./include/crypto/internal/kpp.h plus this whole friend group right here:

All of them are (9) sections, all of them are kernel API, all of them slay in their own way. Go read them, bestie, I'll wait. ⭐

Okay one tiny note because I love you: base is marked Internal in the original, so don't go poking at it in your driver like it's main character energy. It's the crypto core's state, not yours. 🧚

Sign-off time!! This little gem lives over in ./include/crypto/internal, and the page itself is dated October 2026 — yeah, future vibes, we're ahead of schedule 💀. Version/date info courtesy of that same footer, mwah. 🍓💜

📦 where this page comes from