ocs_aes_ccm_op(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

ocs_aes_ccm_op(9) πŸ’… β€” Kernel API Manual

okay so bestie, welcome to the ocs_aes_ccm_op(9) page in the Kernel API Manual. We're doing a CCM operation, and it's giving highkey iconic main character energy. Lowkey obsessed. Let's get into it ✨

πŸ’– NAME πŸ’–

ocs_aes_ccm_op β€” literally performs a CCM operation. That's the whole name, no cap. πŸŽ€

✨ SYNOPSIS ✨

okay so here's the exact signature, keep the tokens cute and untouched:

       int ocs_aes_ccm_op (struct ocs_aes_dev *aes_dev , enum ocs_cipher cipher
       , enum ocs_instruction instruction , dma_addr_t dst_dma_list ,
       dma_addr_t src_dma_list , u32 src_size , u8 *iv , dma_addr_t
       adata_dma_list , u32 adata_size , u8 *in_tag , u32 tag_size );

🌸 ARGUMENTS 🌸

Vibe check: here is every argument, and yes you need all of them bestie:

  • aes_dev β€” the OCS AES device to use. Slay, pick your device. πŸ’…
  • cipher β€” the Cipher to use (AES or SM4). Both ate, no cap. πŸ‘‘
  • instruction β€” the instruction to perform (encrypt or decrypt). Choose your fighter. ⭐
  • dst_dma_list β€” the OCS DMA list mapping output memory. That's the output mapping, iykyk. πŸ“¦
  • src_dma_list β€” the OCS DMA list mapping input payload data. Input payload mapping, bestie. 🧚
  • src_size β€” the amount of data mapped by src_dma_list. Yes, size matters, fr fr. 😭
  • iv β€” the input IV vector. Not me being obsessed with an IV vector. πŸ’œ
  • adata_dma_list β€” the OCS DMA list mapping input A-data. A-data gets its own DMA list, periodt. 🌈
  • adata_size β€” the amount of data mapped by adata_dma_list. Matching size, matching vibe. ✨
  • in_tag β€” input tag. The tag is right there in the name, bestie. 🏷️
  • tag_size β€” the size (in bytes) of in_tag. Bytes, not vibes. πŸ“

πŸ’‘ NOTE πŸ’‘

for encrypt the tag is appended to the ciphertext (in the memory mapped by dst_dma_list). So when you're encrypting, the tag is literally getting appended to the ciphertext in the memory mapped by dst_dma_list, okay? Don't forget that part. πŸ’€

πŸ”₯ RETURN πŸ”₯

0 on success, negative error code otherwise. That's it. Ngl, success is 0; anything negative is giving error. 🫢

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/crypto/intel/keembay/ocs-aes.c, plus:


xoxo bestie πŸ’– β€” source/version: ./drivers/crypto/intel/keembay, date: October 2026. That's the footer, now go slay your CCM operation. πŸ’…

πŸ“¦ where this page comes from