crypto_drop_kpp(9)
β¨ crypto_drop_kpp(9) β¨
okay so bestie, this is from the Kernel API Manual, and it's giving tiny-but-iconic cleanup era. We're talking about crypto_drop_kpp(9) β the page that tells you how to release a spawn that was previously bound. No cap, that's the whole vibe. π«Ά
π NAME π
crypto_drop_kpp β release a spawn previously bound via crypto_grab_kpp(). That's it, that's the lewk. π
β¨ SYNOPSIS β¨
void crypto_drop_kpp (struct crypto_kpp_spawn *spawn );
π ARGUMENTS π
spawnβ the spawn to release. Yes bestie, that's the one. π
Tiny page, big cleanup energy: the only argument is spawn. Keep it cute and keep it exact. π¦
π¦ SEE ALSO π¦
Kernel file: ./include/crypto/internal/kpp.h β and here's the whole bestie lineup, in order:
struct kpp_instance(9)struct crypto_kpp_spawn(9)kpp_crypto_instance(9)kpp_instance(9)kpp_alg_instance(9)kpp_instance_ctx(9)crypto_register_kpp(9)crypto_unregister_kpp(9)kpp_register_instance(9)crypto_grab_kpp(9)crypto_spawn_kpp_alg(9)crypto_spawn_kpp(9)
Sign-off time, bestie: this page lives under source/path ./include/crypto/internal, dated October 2026, and it's serving crypto_drop_kpp(9) realness. mwah πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms