From: Stanley Chu <stanley.chu@mediatek.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Ladvine D Almeida" <Ladvine.DAlmeida@synopsys.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Kim Boojin" <boojin.kim@samsung.com>,
"Kuohong Wang (王國鴻)" <kuohong.wang@mediatek.com>,
"Parshuram Raju Thombare" <pthombar@cadence.com>,
"Barani Muthukumaran" <bmuthuku@qti.qualcomm.com>,
"Satya Tangirala" <satyat@google.com>,
"Christoph Hellwig" <hch@infradead.org>,
"linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH v7 6/9] scsi: ufs: Add inline encryption support to UFS
Date: Mon, 2 Mar 2020 17:17:36 +0800 [thread overview]
Message-ID: <1583140656.10509.2.camel@mtksdccf07> (raw)
In-Reply-To: <1582699394.26304.96.camel@mtksdccf07>
Hi Eric and all,
On Wed, 2020-02-26 at 14:43 +0800, Stanley Chu wrote:
> Hi Eric,
>
> On Tue, 2020-02-25 at 17:12 -0800, Eric Biggers wrote:
> >
> > I'm not sure about the UFS controllers from Synopsys, Cadence, or Samsung, all
> > of which apparently have implemented some form of the crypto support too. But I
> > wouldn't get my hopes up that everyone followed the UFS standard precisely.
> >
> > So if there are no objections, IMO we should make the crypto support opt-in.
> >
> > That makes it even more important to upstream the crypto support for specific
> > hardware like ufs-qcom and ufs-mediatek, since otherwise the ufshcd-crypto code
> > would be unusable even theoretically. I'm volunteering to handle ufs-qcom with
> > https://lkml.kernel.org/linux-block/20200110061634.46742-1-ebiggers@kernel.org/.
> > Stanley, could you send out ufs-mediatek support as an RFC so people can see
> > better what it involves?
>
> Sure, I will send out our RFC patches. Please allow me some time for
> submission.
The ufs-mediatek RFC patch is uploaded as
https://patchwork.kernel.org/patch/11415051/
This patch is rebased to the latest wip-inline-encryption branch in
Eric Biggers's git:
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/
Thanks,
Stanley Chu
_______________________________________________
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-03-02 9:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:50 [f2fs-dev] [PATCH v7 0/9] Inline Encryption Support Satya Tangirala via Linux-f2fs-devel
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 1/9] block: Keyslot Manager for Inline Encryption Satya Tangirala via Linux-f2fs-devel
2020-02-21 17:04 ` Christoph Hellwig
2020-02-21 17:31 ` Christoph Hellwig
2020-02-27 18:14 ` Eric Biggers
2020-02-27 21:25 ` Satya Tangirala via Linux-f2fs-devel
2020-03-05 16:11 ` Christoph Hellwig
2020-02-27 18:48 ` Eric Biggers
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 2/9] block: Inline encryption support for blk-mq Satya Tangirala via Linux-f2fs-devel
2020-02-21 17:22 ` Christoph Hellwig
2020-02-22 0:52 ` Satya Tangirala via Linux-f2fs-devel
2020-02-24 23:34 ` Christoph Hellwig
2020-02-27 18:25 ` Eric Biggers
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption Satya Tangirala via Linux-f2fs-devel
2020-02-21 16:51 ` Randy Dunlap
2020-02-21 17:25 ` Christoph Hellwig
2020-02-21 17:35 ` Christoph Hellwig
2020-02-21 18:34 ` Eric Biggers
2020-02-24 23:36 ` Christoph Hellwig
2020-02-27 19:25 ` Eric Biggers
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 4/9] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala via Linux-f2fs-devel
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 5/9] scsi: ufs: UFS crypto API Satya Tangirala via Linux-f2fs-devel
2020-02-22 4:59 ` Eric Biggers
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 6/9] scsi: ufs: Add inline encryption support to UFS Satya Tangirala via Linux-f2fs-devel
2020-02-21 17:22 ` Christoph Hellwig
2020-02-21 18:11 ` Eric Biggers
2020-02-23 13:47 ` Stanley Chu
2020-02-24 23:37 ` Christoph Hellwig
2020-02-25 7:21 ` Stanley Chu
2020-02-26 1:12 ` Eric Biggers
2020-02-26 6:43 ` Stanley Chu
2020-03-02 9:17 ` Stanley Chu [this message]
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 7/9] fscrypt: add inline encryption support Satya Tangirala via Linux-f2fs-devel
2020-02-21 18:40 ` Eric Biggers
2020-02-22 5:39 ` Eric Biggers
2020-02-26 0:30 ` Eric Biggers
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 8/9] f2fs: " Satya Tangirala via Linux-f2fs-devel
2020-02-21 11:50 ` [f2fs-dev] [PATCH v7 9/9] ext4: " Satya Tangirala via Linux-f2fs-devel
2020-02-22 5:21 ` Eric Biggers
2020-02-21 17:16 ` [f2fs-dev] [PATCH v7 0/9] 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=1583140656.10509.2.camel@mtksdccf07 \
--to=stanley.chu@mediatek.com \
--cc=Ladvine.DAlmeida@synopsys.com \
--cc=bmuthuku@qti.qualcomm.com \
--cc=boojin.kim@samsung.com \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--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=pthombar@cadence.com \
--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).