uv_list_secrets(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… uv_list_secrets β€” the Kernel API Manual girlies are gonna eat this UP

Ok so bestie, welcome to uv_list_secrets(9) β€” yes it's a real one, no I'm not kidding, and yes it's giving "ultraviolet secret list realness" πŸ”₯


✨ NAME ✨

uv_list_secrets β€” literally just "Do a List Secrets UVC." That's the whole vibe. Iconic, concise, no notes πŸŽ€


🌸 SYNOPSIS 🌸

int uv_list_secrets (struct uv_secret_list *buf , u16 start_idx , u16
*rc , u16 *rrc );

Look at her. Four params, one int return, zero drama. Slay πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • buf β€” the buffer you're writing the list into. Heads up: it's gotta be the size of one page, ok? Not vibes-sized, page-sized 🫢
  • start_idx β€” the SMALLEST index that should be included in the list. For the first call? Use 0. Just 0. That's it, that's the whole thing ✨
  • rc β€” pointer to store the return code, or NULL if you're not about that life πŸ™ˆ
  • rrc β€” pointer to store the return reason code, or NULL if you also don't care about that 😭

πŸ’– DESCRIPTION πŸ’–

So what this function actually does: it calls the List Secrets UVC. That's the whole job. Very main character energy πŸ‘‘

The result gets written into buf, and buf needs to be at least one page of writable memory. Not optional, not negotiable, not "ehh probably fine" β€” at least one page, writable, periodt.

And buf is built out of these, in this order:

  • struct uv_secret_list_hdr
  • struct uv_secret_list_item (multiple β€” yes, multiple, she can hold more than one πŸ“)

For start_idx, use _0_ on the first call. Easy.

Now here's the tea β˜• β€” if there are more secrets available but they couldn't fit into the page, then rc comes back as UVC_RC_MORE_DATA. And when that happens? You take uv_secret_list_hdr.next_secret_idx and feed it right back in as your start_idx. Loop it, bestie πŸ”βœ¨


🌈 CONTEXT 🌈

might sleep.

(Yeah. That's it. That's the whole context. She's lowkey sleepy, respect it πŸ˜΄πŸ’œ)


⭐ RETURN ⭐

The UVC condition code. That's what comes back. That's the answer πŸŽ€


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./arch/s390/include/asm/uv.h β€” go read her, she has lore 🧚


πŸ’€ fr fr do NOT forget that buf has to be a full page of writable memory. Not me warning you twice. Okay maybe I am warning you twice. You're welcome 🫢

🌸 That's the page!! Brought to you by the fine folks at ./arch/s390/include/asm, dated October 2026 β€” mwah, love that for us, bye bestie!! πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from