arm_cca_report_new(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ arm_cca_report_new(9) ✨

okay so this is a page straight out of the Kernel API Manual and bestie, it's giving "secret handshake with the hardware" energy πŸ” β€” let's get into it.

πŸŽ€ NAME πŸŽ€

arm_cca_report_new β€” generate a new attestation token, periodt.

🌸 SYNOPSIS 🌸

int arm_cca_report_new (struct tsm_report *report , void *data );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • report β€” pointer to the TSM report context information. literally the whole report vibe lives here.
  • data β€” pointer to the context specific data for this module. this is the module's own little stash of info.

πŸ’… DESCRIPTION πŸ’…

So what it does: it initialises the attestation token generation using the challenge data that you passed in through the TSM descriptor. Then it allocates memory for the attestation token, and retrieves that attestation token on the same CPU where the token generation was initialised. no cap, same CPU, that's the rule πŸ‘‘

About that challenge data β€” it must be at least 32 bytes and no more than 64 bytes. And if you hand over less than 64 bytes, it gets zero padded up to 64 bytes. so don't stress about hitting exactly 64, it'll top you off 🫢

πŸ”₯ RETURN πŸ”₯

  • 0 β€” attestation token generated successfully. slay, we ate πŸ’…
  • -EINVAL β€” a parameter was not valid. one of your args said something unhinged 😭
  • -ENOMEM β€” out of memory. the RAM said "not today" πŸ’€
  • -EFAULT β€” failed to get IPA for memory page(s). the memory page(s) ghosted us πŸ™ˆ

🌈 SEE ALSO 🌈


k that's the whole page bestie, go be iconic with it πŸ§šβ€β™€οΈ this one lives in ./drivers/virt/coco/arm-cca-guest, dated October 2026 β€” mwah, xoxo πŸ’–

πŸ“¦ where this page comes from