From: R Nageswara Sastry <rnsastry@linux.ibm.com>
To: Srish Srinivasan <ssrish@linux.ibm.com>,
linux-integrity@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, naveen@kernel.org,
ajd@linux.ibm.com, zohar@linux.ibm.com, nayna@linux.ibm.com,
msuchanek@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] powerpc/pseries: Correct secvar format representation for static key management
Date: Fri, 4 Jul 2025 14:12:30 +0530 [thread overview]
Message-ID: <ea69919d-87dd-4d5c-b096-620a4050af6f@linux.ibm.com> (raw)
In-Reply-To: <20250610211907.101384-2-ssrish@linux.ibm.com>
On 11/06/25 2:49 AM, Srish Srinivasan wrote:
> On a PLPKS enabled PowerVM LPAR, the secvar format property for static
> key management is misrepresented as "ibm,plpks-sb-unknown", creating
> reason for confusion.
>
> Static key management mode uses fixed, built-in keys. Dynamic key
> management mode allows keys to be updated in production to handle
> security updates without firmware rebuilds.
>
> Define a function named plpks_get_sb_keymgmt_mode() to retrieve the
> key management mode based on the existence of the SB_VERSION property
> in the firmware.
>
> Set the secvar format property to either "ibm,plpks-sb-v<version>" or
> "ibm,plpks-sb-v0" based on the key management mode, and return the
> length of the secvar format property.
>
> Co-developed-by: Souradeep <soura@imap.linux.ibm.com>
> Signed-off-by: Souradeep <soura@imap.linux.ibm.com>
> Signed-off-by: Srish Srinivasan <ssrish@linux.ibm.com>
> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> Reviewed-by: Nayna Jain <nayna@linux.ibm.com>
> Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com>
Tested-by: R Nageswara Sastry <rnsastry@linux.ibm.com>
With the following scenarios:
1. With and with out secure boot by enabling keystore_signed_updates and
keystore_kbytes
2. With Dynamic Key Guest Secure Boot
3. With Static Key Guest Secure Boot
> ---
> Documentation/ABI/testing/sysfs-secvar | 10 ++-
> arch/powerpc/platforms/pseries/plpks-secvar.c | 76 +++++++++++--------
> 2 files changed, 53 insertions(+), 33 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-secvar b/Documentation/ABI/testing/sysfs-secvar
> index 857cf12b0904..f001a4f4bd2e 100644
> --- a/Documentation/ABI/testing/sysfs-secvar
> +++ b/Documentation/ABI/testing/sysfs-secvar
> @@ -22,9 +22,13 @@ Description: A string indicating which backend is in use by the firmware.
> and is expected to be "ibm,edk2-compat-v1".
>
> On pseries/PLPKS, this is generated by the kernel based on the
> - version number in the SB_VERSION variable in the keystore, and
> - has the form "ibm,plpks-sb-v<version>", or
> - "ibm,plpks-sb-unknown" if there is no SB_VERSION variable.
> + version number in the SB_VERSION variable in the keystore. The
> + version numbering in the SB_VERSION variable starts from 1. The
> + format string takes the form "ibm,plpks-sb-v<version>" in the
> + case of dynamic key management mode. If the SB_VERSION variable
> + does not exist (or there is an error while reading it), it takes
> + the form "ibm,plpks-sb-v0", indicating that the key management
> + mode is static.
>
> What: /sys/firmware/secvar/vars/<variable name>
> Date: August 2019
> diff --git a/arch/powerpc/platforms/pseries/plpks-secvar.c b/arch/powerpc/platforms/pseries/plpks-secvar.c
> index 257fd1f8bc19..767e5e8c6990 100644
> --- a/arch/powerpc/platforms/pseries/plpks-secvar.c
> +++ b/arch/powerpc/platforms/pseries/plpks-secvar.c
> @@ -152,39 +152,55 @@ static int plpks_set_variable(const char *key, u64 key_len, u8 *data,
> return rc;
> }
>
> -// PLPKS dynamic secure boot doesn't give us a format string in the same way OPAL does.
> -// Instead, report the format using the SB_VERSION variable in the keystore.
> -// The string is made up by us, and takes the form "ibm,plpks-sb-v<n>" (or "ibm,plpks-sb-unknown"
> -// if the SB_VERSION variable doesn't exist). Hypervisor defines the SB_VERSION variable as a
> -// "1 byte unsigned integer value".
> -static ssize_t plpks_secvar_format(char *buf, size_t bufsize)
> +/*
> + * Return the key management mode.
> + *
> + * SB_VERSION is defined as a "1 byte unsigned integer value", taking values
> + * starting from 1. It is owned by the Partition Firmware and its presence
> + * indicates that the key management mode is dynamic. Any failure in
> + * reading SB_VERSION defaults the key management mode to static. The error
> + * codes -ENOENT or -EPERM are expected in static key management mode. An
> + * unexpected error code will have to be investigated. Only signed variables
> + * have null bytes in their names, SB_VERSION does not.
> + *
> + * Return 0 to indicate that the key management mode is static. Otherwise
> + * return the SB_VERSION value to indicate that the key management mode is
> + * dynamic.
> + */
> +static u8 plpks_get_sb_keymgmt_mode(void)
> {
> - struct plpks_var var = {0};
> - ssize_t ret;
> - u8 version;
> -
> - var.component = NULL;
> - // Only the signed variables have null bytes in their names, this one doesn't
> - var.name = "SB_VERSION";
> - var.namelen = strlen(var.name);
> - var.datalen = 1;
> - var.data = &version;
> -
> - // Unlike the other vars, SB_VERSION is owned by firmware instead of the OS
> - ret = plpks_read_fw_var(&var);
> - if (ret) {
> - if (ret == -ENOENT) {
> - ret = snprintf(buf, bufsize, "ibm,plpks-sb-unknown");
> - } else {
> - pr_err("Error %ld reading SB_VERSION from firmware\n", ret);
> - ret = -EIO;
> - }
> - goto err;
> + u8 mode;
> + ssize_t rc;
> + struct plpks_var var = {
> + .component = NULL,
> + .name = "SB_VERSION",
> + .namelen = 10,
> + .datalen = 1,
> + .data = &mode,
> + };
> +
> + rc = plpks_read_fw_var(&var);
> + if (rc) {
> + if (rc != -ENOENT && rc != -EPERM)
> + pr_info("Error %ld reading SB_VERSION from firmware\n", rc);
> + mode = 0;
> }
> + return mode;
> +}
>
> - ret = snprintf(buf, bufsize, "ibm,plpks-sb-v%hhu", version);
> -err:
> - return ret;
> +/*
> + * PLPKS dynamic secure boot doesn't give us a format string in the same way
> + * OPAL does. Instead, report the format using the SB_VERSION variable in the
> + * keystore. The string, made up by us, takes the form of either
> + * "ibm,plpks-sb-v<n>" or "ibm,plpks-sb-v0", based on the key management mode,
> + * and return the length of the secvar format property.
> + */
> +static ssize_t plpks_secvar_format(char *buf, size_t bufsize)
> +{
> + u8 mode;
> +
> + mode = plpks_get_sb_keymgmt_mode();
> + return snprintf(buf, bufsize, "ibm,plpks-sb-v%hhu", mode);
> }
>
> static int plpks_max_size(u64 *max_size)
--
Thanks and Regards
R.Nageswara Sastry
next prev parent reply other threads:[~2025-07-04 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 21:19 [PATCH v4 0/3] Enhancements to the secvar interface in static key management mode Srish Srinivasan
2025-06-10 21:19 ` [PATCH v4 1/3] powerpc/pseries: Correct secvar format representation for static key management Srish Srinivasan
2025-07-04 8:42 ` R Nageswara Sastry [this message]
2025-06-10 21:19 ` [PATCH v4 2/3] powerpc/secvar: Expose secvars relevant to the key management mode Srish Srinivasan
2025-07-04 8:42 ` R Nageswara Sastry
2025-06-10 21:19 ` [PATCH v4 3/3] integrity/platform_certs: Allow loading of keys in the static " Srish Srinivasan
2025-07-04 8:43 ` R Nageswara Sastry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea69919d-87dd-4d5c-b096-620a4050af6f@linux.ibm.com \
--to=rnsastry@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=naveen@kernel.org \
--cc=nayna@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=ssrish@linux.ibm.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).