From: gjoyce@linux.vnet.ibm.com
To: linux-block@vger.kernel.org
Cc: axboe@kernel.dk, linux-efi@vger.kernel.org,
gjoyce@linux.vnet.ibm.com, nayna@linux.ibm.com,
dhowells@redhat.com, jarkko@kernel.org, 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
Subject: [PATCH v4 0/3] generic and PowerPC SED Opal keystore
Date: Fri, 19 Aug 2022 17:31:35 -0500 [thread overview]
Message-ID: <20220819223138.1457091-1-gjoyce@linux.vnet.ibm.com> (raw)
From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
Generic functions have been defined for accessing SED Opal keys.
The generic functions are defined as weak so that they may be superseded
by keystore specific versions.
PowerPC/pseries versions of these functions provide read/write access
to SED Opal keys in the PLPKS keystore.
The SED block driver has been modified to read the SED Opal
keystore to populate a key in the SED Opal keyring. Changes to the
SED Opal key will be written to the SED Opal keystore.
Patch 3 "keystore access for SED Opal keys" is dependent on:
https://lore.kernel.org/keyrings/20220818143045.680972-4-gjoyce@linux.vnet.ibm.com/T/#u
Changelog
v4:
- scope reduced to cover just SED Opal keys
- base SED Opal keystore is now in SED block driver
- removed use of enum to indicate type
- refactored common code into common function that read and
write use
- removed cast to void
- added use of SED Opal keystore functions to SED block driver
v3:
- No code changes, but per reviewer requests, adding additional
mailing lists(keyring, EFI) for wider review.
v2:
- Include feedback from Gregory Joyce, Eric Richter and
Murilo Opsfelder Araujo.
- Include suggestions from Michael Ellerman.
- Moved a dependency from generic SED code to this patchset.
This patchset now builds of its own.
Greg Joyce (3):
block: sed-opal: SED Opal keystore
powerpc/pseries: PLPKS SED Opal keystore support
block: sed-opal: keystore access for SED Opal keys
arch/powerpc/platforms/pseries/Makefile | 1 +
.../powerpc/platforms/pseries/plpks_sed_ops.c | 124 ++++++++++++++++++
block/Makefile | 2 +-
block/sed-opal-key.c | 23 ++++
block/sed-opal.c | 17 ++-
include/linux/sed-opal-key.h | 15 +++
6 files changed, 179 insertions(+), 3 deletions(-)
create mode 100644 arch/powerpc/platforms/pseries/plpks_sed_ops.c
create mode 100644 block/sed-opal-key.c
create mode 100644 include/linux/sed-opal-key.h
--
gjoyce@linux.vnet.ibm.com
next reply other threads:[~2022-08-19 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 22:31 gjoyce [this message]
2022-08-19 22:31 ` [PATCH v4 1/3] block: sed-opal: SED Opal keystore gjoyce
2022-10-07 18:23 ` Jonathan Derrick
2022-08-19 22:31 ` [PATCH v4 2/3] powerpc/pseries: PLPKS SED Opal keystore support gjoyce
2022-10-07 18:22 ` Jonathan Derrick
2022-10-07 19:09 ` Elliott, Robert (Servers)
2022-11-16 23:44 ` Greg Joyce
2022-08-19 22:31 ` [PATCH v4 3/3] block: sed-opal: keystore access for SED Opal keys gjoyce
2022-10-07 18:21 ` Jonathan Derrick
2022-11-16 23:16 ` 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=20220819223138.1457091-1-gjoyce@linux.vnet.ibm.com \
--to=gjoyce@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brking@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--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=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).