ureq_select(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ureq_select(9) πŸ’–

okay so welcome to the Kernel API Manual, bestie β€” this is the ureq_select(9) page, and it’s literally about selecting the next request in a context. No cap, it’s giving β€œsmall function, important job” energy. πŸ’…


πŸŽ€ NAME πŸŽ€

ureq_select β€” select the next request in a context. periodt. ✨

✨ SYNOPSIS ✨

struct qcomtee_ureq * ureq_select (struct qcomtee_context_data *ctxdata
, size_t ubuf_size , int num_params );

🫢 ARGUMENTS 🫢

  • ctxdata β€” context data for a context to pop a request from. That’s the context we’re working with, iykyk.
  • ubuf_size β€” size of the available buffer for UBUF parameters. That’s the buffer size number, fr fr.
  • num_params β€” number of entries for the TEE parameter array. That’s the count of array entries, no cap.

πŸ¦‹ DESCRIPTION πŸ¦‹

So here’s the vibe: it checks if num_params is large enough to fit the next request arguments. It also checks if ubuf_size is large enough to fit IB buffer arguments. That’s the whole size-check moment, and it’s highkey important. ✨

πŸ”’ CONTEXT πŸ”’

The caller should hold qcomtee_context_data->reqs_lock.

bestie, this is the lock situation: the caller should hold qcomtee_context_data->reqs_lock. Do not skip the lock vibe check. πŸ”

πŸ’« RETURN πŸ’«

On success, it returns a request; on failure, it returns NULL and ERR_PTR. So yeah β€” success gets you a request, failure gets you NULL and ERR_PTR. 😭

πŸ‘€ SEE ALSO πŸ‘€

xoxo, your kernel bestie πŸ’– β€” from the ./drivers/tee/qcomtee source/version, dated October 2026, with ureq_select(9) signing off πŸŽ€βœ¨

πŸ“¦ where this page comes from