plpks_gen_wrapping_key(9)

💖 plpks_gen_wrapping_key(9) — the Linux kernel API manual page, bestie edition 💖

okay so this is the manual page for plpks_gen_wrapping_key(9) and I'm gonna walk you through it like we're chatting at 2am, because honestly it's giving "tiny function, big responsibilities." 🎀

---

✨ NAME ✨

plpks_gen_wrapping_key — generate a brand-new random key with the 'wrapping key' policy set. that's it, that's the whole job, and it slays at it 💅

---

⭐ SYNOPSIS ⭐

int plpks_gen_wrapping_key (void );

like, no arguments, no drama, just vibes and a return value 🦋

---

🌸 ARGUMENTS 🌸

• void — no arguments, bestie. zero. none. the function said "I work alone" and honestly? main character energy 👑

---

🧚 DESCRIPTION 🧚

okay so here's the tea ☕ the H_PKS_GEN_KEY HCALL makes the hypervisor generate a new random key and store that key in a PLPKS object with the provided object label.

ngl the next sentence in the source text is literally With the would be visible to the user. — it just trails off mid-thought 😭 I'm not gonna make up the missing words because that's not the move, so we're relaying it exactly how it sits there, incomplete and iconic.

Now for the part you actually came for: the possible reasons you'd get a negative errno back 🫶

• -ENXIO — if PLPKS is not supported
• -EIO — and this one has layers, bestie:
  • if PLPKS access is blocked due to the LPAR's state
  • if PLPKS modification is blocked due to the LPAR's state
  • if an error occurred while processing the request
• -EINVAL — this one is a whole group chat of "something in the args is off":
  • if invalid authorization parameter
  • if invalid object label parameter
  • if invalid object label len parameter
  • if invalid or unsupported policy declaration
  • if invalid output buffer parameter
  • if invalid output buffer length parameter
• -EPERM — if access is denied 🚫
• -ENOMEM — if there is inadequate memory to perform this operation
• -EBUSY — if unable to handle the request, she's booked and busy 💀
• -EEXIST — if the object label already exists 👀 taken, sorry

---

🔥 RETURN 🔥

On success 0 is returned, a negative errno if not. short, sweet, and to the point — we love a clean contract ✨

---

🌈 SEE ALSO 🌈

Kernel file ./arch/powerpc/platforms/pseries/plpks.c — go read the source, it's right there, iykyk 📖

and the whole PLPKS friend group, clocking in one by one:

• plpks_get_version(9)
• plpks_get_objoverhead(9)
• plpks_get_maxpwsize(9)
• plpks_get_maxobjectsize(9)
• plpks_get_maxobjectlabelsize(9)
• plpks_get_totalsize(9)
• plpks_get_usedspace(9)
• plpks_get_supportedpolicies(9)
• plpks_get_maxlargeobjectsize(9)
• plpks_get_signedupdatealgorithms(9)
• plpks_get_wrappingfeatures(9)
• plpks_get_passwordlen(9)
• plpks_is_available(9)
• plpks_signed_update_var(9)
• plpks_write_var(9)
• plpks_remove_var(9)
• plpks_wrapping_is_supported(9)
• plpks_wrap_object(9)
• plpks_unwrap_object(9)
• plpks_read_os_var(9)
• plpks_read_fw_var(9)
• plpks_read_bootloader_var(9)
• plpks_populate_fdt(9)
• plpks_early_init_devtree(9)

---

💜 quick vibe check reminder: -EEXIST is not a bug, it's just the label already being taken. don't @ me.

---

and that's the page!! written from ./arch/powerpc/platforms/pseries, version stamped October 2026, and yes the title is plpks_gen_wrapping_key(9) — mwah, bye bestie, go generate some keys responsibly 😭💖🌷