uvio_lock_secrets(9)

💖 uvio_lock_secrets(9) — Kernel API Manual 💖

okay so bestie, you found the uvio_lock_secrets(9) page and honestly? it's giving very specific kernel-business energy ✨. Let's get into it 🫶.

✨ NAME ✨

• uvio_lock_secrets — literally performs a Lock Secret Store UVC. periodt 💅

🎀 SYNOPSIS 🎀

int uvio_lock_secrets (struct uvio_ioctl_cb *ioctl );

🌸 ARGUMENTS 🌸

• ioctl — the ioctl control block, bestie 🎀

🦋 DESCRIPTION 🦋

uvio_lock_secrets performs the Lock Secret Store Ultravisor Call. It performs the UV-call and copies the return codes to the ioctl control block 📋. After this call was dispatched successfully, every following Add Secret UVC and Lock Secrets UVC will fail with return code 0x102 😭 — yes, fr fr.

The argument address and size must be 0 — not optional, bestie 💀.

If the Lock Secrets 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 🙈. So don't go side-eyeing the driver for a negative return here, iykyk.

😴 CONTEXT 😴

might sleep — yes, she naps 😴💤

💖 RETURN 💖

0 on success or a negative error code on error ⭐

👑 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_retr_secret(9)

---

and that's the whole page, bestie 🫶 — straight from ./drivers/s390/char, dated October 2026, and signed by none other than uvio_lock_secrets(9) itself 💖✨