From: Eric Biggers <ebiggers@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: linux-scsi@vger.kernel.org, Kim Boojin <boojin.kim@samsung.com>,
Kuohong Wang <kuohong.wang@mediatek.com>,
Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v12 07/12] scsi: ufs: UFS crypto API
Date: Wed, 13 May 2020 11:16:58 -0700 [thread overview]
Message-ID: <20200513181658.GG1243@sol.localdomain> (raw)
In-Reply-To: <20200430115959.238073-8-satyat@google.com>
On Thu, Apr 30, 2020 at 11:59:54AM +0000, Satya Tangirala wrote:
> Introduce functions to manipulate UFS inline encryption hardware
> in line with the JEDEC UFSHCI v2.1 specification and to work with the
> block keyslot manager.
>
> The UFS crypto API will assume by default that a vendor driver doesn't
> support UFS crypto, even if the hardware advertises the capability, because
> a lot of hardware requires some special handling that's not specified in
> the aforementioned JEDEC spec. Each vendor driver must explicity set
> hba->caps |= UFSHCD_CAP_CRYPTO before ufshcd_hba_init_crypto is called to
> opt-in to UFS crypto support.
>
> Signed-off-by: Satya Tangirala <satyat@google.com>
Looks good, you can add:
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-05-13 18:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 11:59 [f2fs-dev] [PATCH v12 00/12] Inline Encryption Support Satya Tangirala via Linux-f2fs-devel
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 01/12] Documentation: Document the blk-crypto framework Satya Tangirala via Linux-f2fs-devel
2020-05-13 16:47 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 02/12] block: Keyslot Manager for Inline Encryption Satya Tangirala via Linux-f2fs-devel
2020-05-13 13:35 ` Christoph Hellwig
2020-05-13 16:59 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 03/12] block: Inline encryption support for blk-mq Satya Tangirala via Linux-f2fs-devel
2020-05-13 13:36 ` Christoph Hellwig
2020-05-13 17:27 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 04/12] block: Make blk-integrity preclude hardware inline encryption Satya Tangirala via Linux-f2fs-devel
2020-05-13 13:37 ` Christoph Hellwig
2020-05-13 17:30 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 05/12] block: blk-crypto-fallback for Inline Encryption Satya Tangirala via Linux-f2fs-devel
2020-05-13 18:05 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 06/12] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala via Linux-f2fs-devel
2020-05-13 18:16 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 07/12] scsi: ufs: UFS crypto API Satya Tangirala via Linux-f2fs-devel
2020-05-13 18:16 ` Eric Biggers [this message]
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 08/12] scsi: ufs: Add inline encryption support to UFS Satya Tangirala via Linux-f2fs-devel
2020-05-13 18:19 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 09/12] fs: introduce SB_INLINECRYPT Satya Tangirala via Linux-f2fs-devel
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 10/12] fscrypt: add inline encryption support Satya Tangirala via Linux-f2fs-devel
2020-04-30 17:04 ` Eric Biggers
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 11/12] f2fs: " Satya Tangirala via Linux-f2fs-devel
2020-04-30 11:59 ` [f2fs-dev] [PATCH v12 12/12] ext4: " Satya Tangirala via Linux-f2fs-devel
2020-04-30 17:02 ` [f2fs-dev] [PATCH v12 00/12] Inline Encryption Support Eric Biggers
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=20200513181658.GG1243@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=bmuthuku@qti.qualcomm.com \
--cc=boojin.kim@samsung.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).