uvio_retr_secret(9)

💅 uvio_retr_secret(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ this one's about uvio_retr_secret, and honestly? it's giving "small function, big responsibilities" energy 🎀

---

🌸 NAME 🌸

uvio_retr_secret — perform a retrieve secret UVC 🕵️‍♀️🔐

---

✨ SYNOPSIS ✨

int uvio_retr_secret (struct uvio_ioctl_cb *uv_ioctl );

like, that's the whole signature. no notes. iconic. 💅

---

🎀 ARGUMENTS 🎀

• uv_ioctl — the ioctl control block, bestie. that's the whole vibe of this parameter. 🫶

---

🦋 DESCRIPTION 🦋

so what does it do? uvio_retr_secret performs the Retrieve Secret Ultravisor Call 🔥 periodt.

here's the tea 🍓: the first two bytes of the argument specify the index of the secret you wanna retrieve. yes, the first two bytes specifically, don't come for me, that's just how it is.

the retrieved secret then gets copied into the argument buffer — but only if there is enough space 🙈 so like, vibe check your buffer first, fr fr.

and the argument length? it must be at least two bytes and at max 8192 bytes ⭐ that's the range, no cap. go outside it and, well… don't. 💀

---

🌈 CONTEXT 🌈

might sleep 😴💤

(and yes, that means what it means — don't be doing this in a context where sleeping is a no-no, bestie. ngl that's important.)

---

⭐ RETURN ⭐

• 0 on success 🎉 slay
• a negative error code on error 😭 not slay

---

👑 SEE ALSO 👑

• Kernel file ./drivers/s390/char/uvdevice.c
• uvio_uvdev_info(9)
• uvio_attestation(9)
• uvio_add_secret(9)
• uvio_list_secrets(9)
• uvio_lock_secrets(9)

go read those too, they're all in the same friend group 🧚‍♀️💜

---

lowkey reminder: keep every byte count and every option name exactly as written above — the vibes are flexible, the facts are not 💖

---

and that's a wrap, bestie 🎀 this page lives in ./drivers/s390/char, dated October 2026, and it's from the Kernel API Manual itself — so you know it's legit 👑✨ mwah, ty for reading, ily, go retrieve those secrets responsibly 💅🌟