plpks_signed_update_var(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– plpks_signed_update_var(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for plpks_signed_update_var(9) β€” manual name folded in right at the top, we're being cute and efficient. ✨

🌸 NAME 🌸

plpks_signed_update_var β€” update the specified authenticated variable. πŸ’…

✨ SYNOPSIS ✨

int plpks_signed_update_var (struct plpks_var *var , u64 flags );

🫢 ARGUMENTS 🫢

  • var β€” authenticated variable to be updated. πŸŽ€
  • flags β€” signed update request operation flags. 🚩

πŸ”₯ DESCRIPTION πŸ”₯

so basically, the H_PKS_SIGNED_UPDATE HCALL is the one doing a signed update to an object in the PLPKS. no cap. πŸ’«

The object must have the signed update policy flag set. like, that is not optional, bestie. 🚨

Possible reasons for the returned errno values β€” because errno loves to be dramatic:

  • -ENXIO β€” if PLPKS is not supported. πŸ’€
  • -EIO β€” 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 β€” if invalid authorization parameter; if invalid object label parameter; if invalid object label len parameter; if invalid or unsupported policy declaration; if invalid signed update flags; if invalid input data parameter; if invalid input data len parameter; if invalid continue token parameter. πŸ™ˆ
  • -EPERM β€” if access is denied. 🚫
  • -ENOMEM β€” if there is inadequate memory to perform the operation. 🧠πŸ’₯
  • -EBUSY β€” if unable to handle the request or long running operation initiated, retry later. ⏳

🌈 RETURN 🌈

On success 0 is returned, a negative errno if not. that's the whole vibe. πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹


mwah! this page's source/version is ./arch/powerpc/platforms/pseries, dated October 2026. stay slay, kernel bestie. πŸ’–βœ¨

πŸ“¦ where this page comes from