STRUCT TEE_IOCL_SUPP_RECV_ARG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct tee_iocl_supp_recv_arg(9) ✨

okay so bestie, we're in the Kernel API Manual, section 9, and today's main character is struct tee_iocl_supp_recv_arg β€” literally the thing that catches an incoming request for a supplicant function 🫢 ngl it's a glow-up of a struct, let's get into it.


🌸 NAME 🌸

struct tee_iocl_supp_recv_arg β€” Receive a request for a supplicant function πŸ’Œ


πŸ¦‹ SYNOPSIS πŸ¦‹

struct tee_iocl_supp_recv_arg {
    __u32 func;
    __u32 num_params;
    struct tee_ioctl_param params[];
 };

that's the whole fit, no cap ✨


πŸ’… Members πŸ’…

  • func β€” [in] supplicant function. this is the input girlie telling you which function we're talking about πŸ’–
  • num_params β€” [in/out] number of struct tee_ioctl_param entries in params. she works both directions, we love a versatile icon πŸ‘‘
  • params β€” array of ioctl parameters. the whole squad of them 🌈

πŸŽ€ Description πŸŽ€

okay this is the part you actually need to remember, so listen up πŸ”₯

num_params is the number of params that tee-supplicant has room to receive when input, and num_params is the number of actual params tee-supplicant receives when output.

so like β€” same field, two completely different vibes depending on which way the data's flowing. input: how much room she has 🫢 output: how much actually showed up 😭 don't mix them up, i'm begging.


⭐ SEE ALSO ⭐

Kernel file ./include/uapi/linux/tee.h β€” and the whole extended friend group:


πŸ’€ reminder that num_params changes meaning between input and output β€” that's not a bug, that's just her being an icon. read the Description again if you're confused, i got you 🧚

okay bye bestie, that's the page!! this one lives in ./include/uapi/linux, dated October 2026, and it's filed under struct tee_...upp_recv_arg(9) β€” slay, go read the source, periodt πŸ’œπŸŽ€

πŸ“¦ where this page comes from