__make_folio_secure(9)

NAME ✨

okay so bestie, this is __make_folio_secure(9) from the Kernel API Manual, and the whole assignment is literally right there in the name: make a folio secure 💅 no cap.

---

🌸 SYNOPSIS 🌸

       int __make_folio_secure (struct folio *folio , struct uv_cb_header *uvcb
       );

Like, the vibe check is right there: it returns an int, and it takes a struct folio *folio plus a struct uv_cb_header *uvcb.

---

🎀 ARGUMENTS 🎀

• folio — the folio to make secure. This is the main-character folio of the whole operation.
• uvcb — the uvcb that describes the UVC to be used. It's giving "instructions for the UVC," periodt.

---

🦋 DESCRIPTION 🦋

The folio folio will be made secure if possible, and uvcb will be passed as-is to the UVC. That's it. No extra glow-up, no copy, no remix — uvcb goes in exactly as it is 💖.

---

💜 RETURN 💜

• 0 — success, slay ✨
• -EBUSY — if the folio is in writeback or has too many references
• -EAGAIN — if the UVC needs to be attempted again
• -ENXIO — if the address is not mapped
• -EINVAL — if the UVC failed for other reasons

---

🔥 CONTEXT 🔥

Okay so before you call this, bestie, the caller must hold exactly one extra reference on the folio — yes, it's the same logic as split_folio — and the folio must be locked. Not optional. Locked folio or no deal 🔒.

---

🌈 SEE ALSO 🌈

• Kernel file ./arch/s390/kernel/uv.c
• s390_wiggle_split_folio(9)
• uv_find_secret(9)
• uv_retrieve_secret(9)

---

xoxo 💅 — source/version: ./arch/s390/kernel, date: October 2026, for __make_folio_secure(9). bye bestie 🫶