skcipher_re...set_callback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual page for skcipher_request_set_callback(9) β€” yes, the whole function name is a mouthful, but she’s iconic πŸ’…


🌸 NAME 🌸

skcipher_request_set_callback β€” set asynchronous callback function. periodt πŸ’–

✨ SYNOPSIS ✨

void skcipher_request_set_callback (struct skcipher_request *req , u32
       flags , crypto_completion_t compl , void *data );

πŸŽ€ ARGUMENTS πŸŽ€

okay here’s the cast, bestie:

  • req β€” request handle 🫢
  • flags β€” specify zero or an ORing of the flags:
    • CRYPTO_TFM_REQ_MAY_BACKLOG β€” the request queue may back log and increase the wait queue beyond the initial maximum size;
    • CRYPTO_TFM_REQ_MAY_SLEEP β€” the request processing may sleep.
  • compl β€” callback function pointer to be registered with the request handle πŸ’…
  • data β€” the data pointer refers to memory that is not used by the kernel crypto API, but provided to the callback function for it to use. Here, the caller can provide a reference to memory the callback function can operate on. As the callback function is invoked asynchronously to the related functionality, it may need to access data structures of the related functionality which can be referenced using this pointer. The callback function can access the memory via the "data" field in the crypto_async_request data structure provided to the callback function. πŸ’–

πŸ’… DESCRIPTION πŸ’…

This function is the one that lets you set the callback function that gets triggered once the cipher operation completes. The callback function is registered with the skcipher_request handle and must comply with the following template:

            void callback_function(struct crypto_async_request *req, int error)

πŸ”₯ SEE ALSO πŸ”₯

the whole group chat pulls up:


xoxo, your Unix bestie πŸ’– β€” source/version + date situation: ./include/crypto, October 2026 ✨

πŸ“¦ where this page comes from