From: Andrew Donnellan <ajd@linux.ibm.com>
To: gjoyce@linux.vnet.ibm.com, linux-block@vger.kernel.org
Cc: axboe@kernel.dk, linux-efi@vger.kernel.org, nayna@linux.ibm.com,
me@benboeckel.net, keyrings@vger.kernel.org,
jonathan.derrick@linux.dev, brking@linux.vnet.ibm.com,
akpm@linux-foundation.org, msuchanek@suse.de,
linuxppc-dev@lists.ozlabs.org, elliott@hpe.com
Subject: Re: [PATCH 4/4] powerpc/pseries: update SED for PLPKS api changes
Date: Mon, 15 May 2023 15:52:48 +1000 [thread overview]
Message-ID: <aebe6be66ad982dafa072848246255b9a32e8903.camel@linux.ibm.com> (raw)
In-Reply-To: <20230505194402.2079010-5-gjoyce@linux.vnet.ibm.com>
On Fri, 2023-05-05 at 14:44 -0500, gjoyce@linux.vnet.ibm.com wrote:
> From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
>
> Changes to the PLPKS API require minor updates to the SED Opal
> PLPKS keystore code.
>
> Signed-off-by: Greg Joyce <gjoyce@linux.vnet.ibm.com>
[+ Nayna]
This patch will need to be squashed with patch 2.
> ---
> arch/powerpc/platforms/pseries/Kconfig | 6 +++++
> arch/powerpc/platforms/pseries/Makefile | 2 +-
> .../powerpc/platforms/pseries/plpks_sed_ops.c | 22 +++++------------
> --
> block/Kconfig | 1 +
> 4 files changed, 13 insertions(+), 18 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/Kconfig
> b/arch/powerpc/platforms/pseries/Kconfig
> index 21b22bf16ce6..c2f8a29e7b9b 100644
> --- a/arch/powerpc/platforms/pseries/Kconfig
> +++ b/arch/powerpc/platforms/pseries/Kconfig
> @@ -163,6 +163,12 @@ config PSERIES_PLPKS
> # This option is selected by in-kernel consumers that require
> # access to the PKS.
>
> +config PSERIES_PLPKS_SED
> + depends on PPC_PSERIES
> + bool
> + # This option is selected by in-kernel consumers that require
> + # access to the SED PKS keystore.
> +
> config PAPR_SCM
> depends on PPC_PSERIES && MEMORY_HOTPLUG && LIBNVDIMM
> tristate "Support for the PAPR Storage Class Memory
> interface"
> diff --git a/arch/powerpc/platforms/pseries/Makefile
> b/arch/powerpc/platforms/pseries/Makefile
> index 4242aed0d5d3..1476c5e4433c 100644
> --- a/arch/powerpc/platforms/pseries/Makefile
> +++ b/arch/powerpc/platforms/pseries/Makefile
> @@ -29,7 +29,7 @@ obj-$(CONFIG_PPC_SVM) += svm.o
> obj-$(CONFIG_FA_DUMP) += rtas-fadump.o
> obj-$(CONFIG_PSERIES_PLPKS) += plpks.o
> obj-$(CONFIG_PPC_SECURE_BOOT) += plpks-secvar.o
> -obj-$(CONFIG_PSERIES_PLPKS_SED) += plpks-sed.o
> +obj-$(CONFIG_PSERIES_PLPKS_SED) += plpks_sed_ops.o
I think you could just use obj-$(CONFIG_BLK_SED_OPAL) and then there
wouldn't be a need to introduce a new option? Unless there's going to
be a second consumer.
> obj-$(CONFIG_SUSPEND) += suspend.o
> obj-$(CONFIG_PPC_VAS) += vas.o vas-sysfs.o
>
> diff --git a/arch/powerpc/platforms/pseries/plpks_sed_ops.c
> b/arch/powerpc/platforms/pseries/plpks_sed_ops.c
> index 086934b319a9..c1d08075e850 100644
> --- a/arch/powerpc/platforms/pseries/plpks_sed_ops.c
> +++ b/arch/powerpc/platforms/pseries/plpks_sed_ops.c
> @@ -14,7 +14,7 @@
> #include <linux/string.h>
> #include <linux/ioctl.h>
> #include <linux/sed-opal-key.h>
> -#include "plpks.h"
> +#include <asm/plpks.h>
>
> /*
> * structure that contains all SED data
> @@ -28,9 +28,6 @@ struct plpks_sed_object_data {
> u_char key[32];
> };
>
> -#define PLPKS_PLATVAR_POLICY WORLDREADABLE
> -#define PLPKS_PLATVAR_OS_COMMON 4
> -
> #define PLPKS_SED_OBJECT_DATA_V0 0
> #define PLPKS_SED_MANGLED_LABEL "/default/pri"
> #define PLPKS_SED_COMPONENT "sed-opal"
> @@ -50,8 +47,8 @@ void plpks_init_var(struct plpks_var *var, char
> *keyname)
> var->name = PLPKS_SED_MANGLED_LABEL;
> var->namelen = strlen(keyname);
> }
> - var->policy = PLPKS_PLATVAR_POLICY;
> - var->os = PLPKS_PLATVAR_OS_COMMON;
> + var->policy = PLPKS_WORLDREADABLE;
> + var->os = PLPKS_VAR_COMMON;
> var->data = NULL;
> var->datalen = 0;
> var->component = PLPKS_SED_COMPONENT;
> @@ -64,28 +61,19 @@ int sed_read_key(char *keyname, char *key, u_int
> *keylen)
> {
> struct plpks_var var;
> struct plpks_sed_object_data data;
> - u_int offset;
> int ret;
> u_int len;
>
> plpks_init_var(&var, keyname);
> - var.data = &data;
> + var.data = (u8 *)&data;
> var.datalen = sizeof(data);
>
> ret = plpks_read_os_var(&var);
> if (ret != 0)
> return ret;
>
> - offset = offsetof(struct plpks_sed_object_data, key);
> - if (offset > var.datalen) {
> - return -EINVAL;
> - }
> -
> - len = min(be32_to_cpu(data.key_len), *keylen);
> -
> + len = min_t(u16, be32_to_cpu(data.key_len), var.datalen);
> memcpy(key, data.key, len);
> - kfree(var.data);
> -
> key[len] = '\0';
> *keylen = len;
>
> diff --git a/block/Kconfig b/block/Kconfig
> index 76b23114fdeb..75d4db34df5a 100644
> --- a/block/Kconfig
> +++ b/block/Kconfig
> @@ -182,6 +182,7 @@ config BLK_SED_OPAL
> bool "Logic for interfacing with Opal enabled SEDs"
> depends on KEYS
> select PSERIES_PLPKS if PPC_PSERIES
> + select PSERIES_PLPKS_SED if PPC_PSERIES
> help
> Builds Logic for interfacing with Opal enabled controllers.
> Enabling this option enables users to setup/unlock/lock
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2023-05-15 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 19:43 [PATCH v5 0/4] generic and PowerPC SED Opal keystore gjoyce
2023-05-05 19:43 ` [PATCH 1/4] block:sed-opal: " gjoyce
2023-05-10 22:50 ` Jarkko Sakkinen
2023-06-01 14:29 ` Greg Joyce
2023-05-05 19:44 ` [PATCH 2/4] powerpc/pseries: PLPKS SED Opal keystore support gjoyce
2023-05-05 19:44 ` [PATCH 3/4] block: sed-opal: keystore access for SED Opal keys gjoyce
2023-05-05 19:44 ` [PATCH 4/4] powerpc/pseries: update SED for PLPKS api changes gjoyce
2023-05-15 5:52 ` Andrew Donnellan [this message]
2023-06-01 14:27 ` Greg Joyce
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=aebe6be66ad982dafa072848246255b9a32e8903.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brking@linux.vnet.ibm.com \
--cc=elliott@hpe.com \
--cc=gjoyce@linux.vnet.ibm.com \
--cc=jonathan.derrick@linux.dev \
--cc=keyrings@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=me@benboeckel.net \
--cc=msuchanek@suse.de \
--cc=nayna@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).