kpp_request_set_callback(9)

📦 version 7.3.1, in nixpkgs unstable

💅 kpp_request_set_callback(9) — like, the Kernel API Manual one, bestie

okay so picture this: you're deep in kernel land, you've got a kpp_request just sitting there, and you need to know when your async op is done done. That's this function. It sets an asynchronous callback, and honestly? It's giving main character energy for the whole request lifecycle ✨

✨ SYNOPSIS ✨

void kpp_request_set_callback (struct kpp_request *req , u32 flgs ,
       crypto_completion_t cmpl , void *data );

look at that signature. four args. void return. no notes. 🎀

🌸 ARGUMENTS 🌸

  • req — the request that the callback will be set for. this is your request, bestie, the one you're emotionally attached to now 🫶
  • flgs — these specify, for instance, if the operation may backlog. like, it might have to wait its turn in the queue. respect the queue 💅
  • cmpl — the callback which will be called. type crypto_completion_t. this is the whole point of the function, lowkey the star of the show 👑
  • data — private data used by the caller. your little secret stash. nobody else's business 🙈

💖 DESCRIPTION 💖

So here's the vibe: the callback will be called when an asynchronous operation on a given request is finished. that's it. that's the sentence. and it's iconic.

like, you hand over your req, your flgs, your cmpl and your data, and the kernel goes "noted, bestie" and then eventually — when the async op wraps up — your callback fires. no cap. periodt. 🔥

fr fr, this is the async notification hookup for Key-agreement Protocol Primitives. don't sleep on it.

🦋 SEE ALSO 🦋

go read them all, i'll wait. actually no i won't, i'll be reading them too. 🌈⭐

and that's the whole page, bestie!! it lives under ./include/crypto in the Kernel API Manual, and it's dated October 2026 — so yeah, future-coded of it. mwah. 💋🧚‍♀️💜

📦 where this page comes from