uvio_add_secret(9)

💖 NAME 💖

okay bestie, welcome to uvio_add_secret(9) — yes, that's the page, straight from the Kernel API Manual. it performs an Add Secret UVC. iconic behavior. 🫶

✨ SYNOPSIS ✨

int uvio_add_secret (struct uvio_ioctl_cb *uv_ioctl );

🎀 ARGUMENTS 🎀

• uv_ioctl — the ioctl control block. that's the arg, periodt. 💅

🦋 DESCRIPTION 🦋

okay so uvio_add_secret performs the Add Secret Ultravisor Call. literally what it says on the tin. ✨

The given userspace argument address and size are verified to be valid, but every other check is made by the Ultravisor (UV). so bestie, UV errors won't result in a negative return value — that's a big deal. The request is then copied to kernelspace, the UV-call is performed, and the results are copied back to userspace. 💫

The argument has to point to an Add Secret Request Control Block — which is an encrypted and cryptographically verified request that inserts a protected guest's secrets into the Ultravisor for later use. no cap, that's the whole point. 🔐

If the Add Secret UV facility is not present, UV will return invalid command rc. This won't be fenced in the driver and does not result in a negative return value. periodt. 💀

☁️ CONTEXT ☁️

might sleep 😴

🌈 RETURN 🌈

0 on success or a negative error code on error. simple as that, bestie. 🎀

🌸 SEE ALSO 🌸

Kernel file ./drivers/s390/char/uvdevice.c, plus uvio_uvdev_info(9), uvio_attestation(9), uvio_list_secrets(9), uvio_lock_secrets(9), and uvio_retr_secret(9). go read those next, iykyk. 🦋

---

mwah 💋 — source/version + date vibes: ./drivers/s390/char · October 2026. and that's the whole uvio_add_secret(9) page, bestie. 💖