spu_aead_rx_sg_create(9)

💫 spu_aead_rx_sg_create — the Kernel API Manual moment ✨

okay so bestie, we're in the Kernel API Manual (spu_aead_rx_sg_create(9), section 9, kernel-space teas) and this function is literally the person who builds the scatterlist of buffers used to receive a SPU response message for an AEAD request 🎀 and yes, it also includes buffers to catch SPU message headers and the response data. iykyk 💅

---

🌸 NAME 🌸

spu_aead_rx_sg_create — build up the scatterlist of buffers used to receive a SPU response message for an AEAD request 💖 includes buffers to catch SPU message headers and the response data, no cap.

---

✨ SYNOPSIS ✨

int spu_aead_rx_sg_create (struct brcm_message *mssg , struct
       aead_request *req , struct iproc_reqctx_s *rctx , u8 rx_frag_num ,
       unsigned int assoc_len , u32 ret_iv_len , unsigned int resp_len ,
       unsigned int digestsize , u32 stat_pad_len );

like, that's nine whole arguments bestie, she's highkey doing the most and we love her for it 🫶

---

🦋 ARGUMENTS 🦋

• mssg — the mailbox message containing the receive sg 📬 that's her whole ride.
• req — the Crypto API request, main character energy fr.
• rctx — the crypto request context, the little sidekick carrying the details.
• rx_frag_num — number of scatterlist elements required to hold the SPU response message. count 'em, bestie.
• assoc_len — length of associated data included in the crypto request.
• ret_iv_len — length of IV returned in response 🎀
• resp_len — number of bytes of response data expected to be written to dst buffer from crypto API.
• digestsize — length of hash digest, in bytes ⭐
• stat_pad_len — number of bytes required to pad the STAT field to a 4-byte boundary. yes she's padding, she's aligned, she's iconic 💅

---

💜 DESCRIPTION 💜

so the scatterlist that gets allocated here is freed in spu_chunk_cleanup when the request completes — and it happens whether the request is handled successfully or there is an error 😭 so no leaks, she cleans up after herself either way. periodt.

---

🔥 RETURN 🔥

0 if successful, < 0 if an error. that's it, that's the vibe check 🌈

---

🌼 SEE ALSO 🌼

kernel file ./drivers/crypto/bcm/cipher.c and the whole friend group:

• select_channel(9)
• spu_skcipher_rx_sg_create(9)
• spu_skcipher_tx_sg_create(9)
• handle_skcipher_req(9)
• handle_skcipher_resp(9)
• spu_ahash_rx_sg_create(9)
• spu_ahash_tx_sg_create(9)
• handle_ahash_req(9)
• spu_hmac_outer_hash(9)
• ahash_req_done(9)
• handle_ahash_resp(9)
• spu_aead_tx_sg_create(9)
• handle_aead_req(9)
• handle_aead_resp(9)
• spu_chunk_cleanup(9)
• finish_req(9)
• spu_rx_callback(9)
• skcipher_enqueue(9)
• spu_no_incr_hash(9)
• aead_gcm_esp_setkey(9)
• rfc4543_gcm_esp_setkey(9)
• aead_ccm_esp_setkey(9)
• spu_functions_register(9)
• spu_mb_init(9)

---

bestie reminder: that scatterlist is freed in spu_chunk_cleanup on completion, success or error 💀 don't go holding onto it.

---

and that's the page! 🧚 from ./drivers/crypto/bcm, dated October 2026 — stay hydrated, keep your buffers aligned, and slay 💖✨🎀