From: Eric Biggers <ebiggers@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] Inline Encryption Support for UFS
Date: Wed, 17 Jun 2020 09:24:46 -0700 [thread overview]
Message-ID: <20200617162446.GA1138@sol.localdomain> (raw)
In-Reply-To: <20200617081841.218985-1-satyat@google.com>
On Wed, Jun 17, 2020 at 08:18:38AM +0000, Satya Tangirala wrote:
> This patch series adds support for inline encryption to UFS using
> the inline encryption support in the block layer. It follows the JEDEC
> UFSHCI v2.1 specification, which defines inline encryption for UFS.
> This patch series is based on v5.8-rc1.
>
> Patch 1 introduces the crypto registers and struct definitions defined
> in the UFSHCI v2.1 spec.
>
> Patch 2 introduces functions to manipulate the UFS inline encryption
> hardware (again in line with the UFSHCI v2.1 spec) via the block
> layer keyslot manager. Device specific drivers must set the
> UFSHCD_CAP_CRYPTO in hba->caps before ufshcd_hba_init_crypto is called
> to opt-in to inline encryption support.
>
> Patch 3 wires up ufshcd.c with the UFS crypto API introduced in Patch 2.
>
> Satya Tangirala (3):
> scsi: ufs: UFS driver v2.1 spec crypto additions
> scsi: ufs: UFS crypto API
> scsi: ufs: Add inline encryption support to UFS
>
> drivers/scsi/ufs/Kconfig | 9 ++
> drivers/scsi/ufs/Makefile | 1 +
> drivers/scsi/ufs/ufshcd-crypto.c | 226 +++++++++++++++++++++++++++++++
> drivers/scsi/ufs/ufshcd-crypto.h | 60 ++++++++
> drivers/scsi/ufs/ufshcd.c | 46 ++++++-
> drivers/scsi/ufs/ufshcd.h | 24 ++++
> drivers/scsi/ufs/ufshci.h | 67 ++++++++-
> 7 files changed, 426 insertions(+), 7 deletions(-)
> create mode 100644 drivers/scsi/ufs/ufshcd-crypto.c
> create mode 100644 drivers/scsi/ufs/ufshcd-crypto.h
Note that these patches previously went through a number of iterations as part
of the "Inline Encryption Support" patchset (last version was v13:
https://lkml.kernel.org/r/20200514003727.69001-1-satyat@google.com). There are
no significant changes from v13, right? It would be helpful to mention this in
the cover letter.
It would also be helpful to describe how this was tested at least in the cover
letter, but maybe in one of the commit messages too. For example I and two
other people have tested the Qualcomm ICE support on top of this with
https://lkml.kernel.org/linux-scsi/20200501045111.665881-1-ebiggers@kernel.org/.
(BTW, I'll be rebasing, re-testing, and re-sending those patches soon.)
Mediatek has also tested this with
https://lkml.kernel.org/linux-scsi/20200304022101.14165-1-stanley.chu@mediatek.com/.
- Eric
prev parent reply other threads:[~2020-06-17 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 8:18 [PATCH 0/3] Inline Encryption Support for UFS Satya Tangirala
2020-06-17 8:18 ` [PATCH 1/3] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala
2020-06-17 16:26 ` Eric Biggers
2020-06-17 8:18 ` [PATCH 2/3] scsi: ufs: UFS crypto API Satya Tangirala
2020-06-17 16:27 ` Eric Biggers
2020-06-17 8:18 ` [PATCH 3/3] scsi: ufs: Add inline encryption support to UFS Satya Tangirala
2020-06-17 16:28 ` Eric Biggers
2020-06-18 2:52 ` Satya Tangirala
2020-06-17 16:24 ` Eric Biggers [this message]
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=20200617162446.GA1138@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satyat@google.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