From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
To: linux-block@vger.kernel.org, axboe@kernel.dk
Cc: nayna@linux.ibm.com, ndesaulniers@google.com, nathan@kernel.org,
okozina@redhat.com, jarkko@kernel.org,
jonathan.derrick@linux.dev, brking@linux.vnet.ibm.com,
akpm@linux-foundation.org, msuchanek@suse.de,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v8 0/3] generic and PowerPC SED Opal keystore
Date: Tue, 17 Oct 2023 10:09:15 -0500 [thread overview]
Message-ID: <8fa5c9fdebd07f654c511d80d41a35817bdc3d4d.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20231004201957.1451669-1-gjoyce@linux.vnet.ibm.com>
Hi Jens,
I've addressed all the comments/issues on v7 of the patchset and
haven't received any feedback on v8. Is there anything else that you'd
like to see before this can be included?
Thanks,
Greg
On Wed, 2023-10-04 at 15:19 -0500, gjoyce@linux.vnet.ibm.com wrote:
> From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
>
> This patchset has gone through numerous rounds of review and
> all comments/suggetions have been addressed. The reviews have
> covered all relevant areas including reviews by block and keyring
> developers as well as the SED Opal maintainer.
>
> TCG SED Opal is a specification from The Trusted Computing Group
> that allows self encrypting storage devices (SED) to be locked at
> power on and require an authentication key to unlock the drive.
>
> PowerPC/pseries versions of key 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.
>
>
> Changelog
> v8: - rebased to 6.6-rc4
> - fixed issues using clang (thanks Nathan Chancellor and Nick
> Desaulniers)
> - fixed crash if PLPKS is not present for pseries (thanks
> Michael
> Ellerman)
>
> v7: - rebased to for-6.5/block
>
> v6: - squashed two commits (suggested by Andrew Donnellan)
>
> v5: - updated to reflect changes in PLPKS API
>
> 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
> block: sed-opal: keystore access for SED Opal keys
> powerpc/pseries: PLPKS SED Opal keystore support
>
> arch/powerpc/platforms/pseries/Kconfig | 6 +
> arch/powerpc/platforms/pseries/Makefile | 1 +
> .../powerpc/platforms/pseries/plpks_sed_ops.c | 131
> ++++++++++++++++++
> block/Kconfig | 1 +
> block/sed-opal.c | 18 ++-
> include/linux/sed-opal-key.h | 26 ++++
> 6 files changed, 181 insertions(+), 2 deletions(-)
> create mode 100644 arch/powerpc/platforms/pseries/plpks_sed_ops.c
> create mode 100644 include/linux/sed-opal-key.h
>
next prev parent reply other threads:[~2023-10-17 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 20:19 [PATCH v8 0/3] generic and PowerPC SED Opal keystore gjoyce
2023-10-04 20:19 ` [PATCH v8 1/3] block:sed-opal: " gjoyce
2023-10-04 20:19 ` [PATCH v8 2/3] block: sed-opal: keystore access for SED Opal keys gjoyce
2023-10-04 20:19 ` [PATCH v8 3/3] powerpc/pseries: PLPKS SED Opal keystore support gjoyce
2023-10-17 15:09 ` Greg Joyce [this message]
2023-10-17 15:24 ` [PATCH v8 0/3] generic and PowerPC SED Opal keystore Jens Axboe
2023-10-17 15:24 ` Jens Axboe
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=8fa5c9fdebd07f654c511d80d41a35817bdc3d4d.camel@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=jarkko@kernel.org \
--cc=jonathan.derrick@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
--cc=nathan@kernel.org \
--cc=nayna@linux.ibm.com \
--cc=ndesaulniers@google.com \
--cc=okozina@redhat.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).