spum_cipher_req_finish(9)

🌸 NAME 🌸

okay so this is spum_cipher_req_finish(9) from the Kernel API Manual, and she is here to finish building a SPU request message header for a block cipher request. no cap, she assumes much of the header was already filled in at setkey() time in spu_cipher_req_init(). iconic setup behavior 💅

✨ SYNOPSIS ✨

void spum_cipher_req_finish (u8 *spu_hdr , u16 spu_req_hdr_len ,
unsigned int is_inbound , struct spu_cipher_parms *cipher_parms ,
unsigned int data_size );

🎀 ARGUMENTS 🎀

• spu_hdr — start of the request message header (the MH field). literally where the header begins 🫶
• spu_req_hdr_len — length in bytes of the SPU request header. count those bytes, bestie ✨
• is_inbound — 0 encrypt, 1 decrypt. that's the whole vibe check right there 🔥
• cipher_parms — parameters describing the cipher operation to be performed. the cipher's little info packet 💜
• data_size — length of the data in the BD field. yes, the BD field, keep up 💅

🦋 DESCRIPTION 🦋

Assumes much of the header was already filled in at setkey time in spum_cipher_req_init. and bestie, spum_cipher_req_init fills in the encryption key. that's the whole tea ☕✨

🌈 SEE ALSO 🌈

the whole squad is here, iykyk:

• Kernel file ./drivers/crypto/bcm/spu.c
• spum_ns2_ctx_max_payload(9)
• spum_nsp_ctx_max_payload(9)
• spum_response_hdr_len(9)
• spum_hash_pad_len(9)
• spum_gcm_ccm_pad_len(9)
• spum_assoc_resp_len(9)
• spum_aead_ivlen(9)
• spum_hash_type(9)
• spum_digest_size(9)
• spum_create_request(9)
• spum_cipher_req_init(9)
• spum_request_pad(9)
• spum_xts_tweak_in_payload(9)
• spum_tx_status_len(9)
• spum_rx_status_len(9)
• spum_status_process(9)
• spum_ccm_update_iv(9)
• spum_wordalign_padlen(9)

xoxo, signed off from ./drivers/crypto/bcm, October 2026 💖🌷