From: Christoph Hellwig <hch@infradead.org>
To: Ladvine D Almeida <Ladvine.DAlmeida@synopsys.com>
Cc: Milan Broz <gmazyland@gmail.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Manjunath M Bettegowda <Manjunath.MB@synopsys.com>,
Prabu Thangamuthu <Prabu.T@synopsys.com>,
Tejas Joglekar <Tejas.Joglekar@synopsys.com>,
device-mapper development <dm-devel@redhat.com>,
Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
Date: Fri, 1 Jun 2018 01:16:42 -0700 [thread overview]
Message-ID: <20180601081642.GA25973@infradead.org> (raw)
In-Reply-To: <BD7FB879CC136E419544C8E2AE7B9C3020BB94@IN01WEMBXA.internal.synopsys.com>
On Wed, May 30, 2018 at 02:52:07PM +0000, Ladvine D Almeida wrote:
> when the optional argument "perform_inline_encrypt" is set, we are not unconditionally sending the bio
> to the block devices. The steps are explained below:
> 1. user invokes the dm-setup command with the registered cipher "xts" and with the optional argument
> "perform_inline_encrypt".
> 2. dm-setup invokes the setkey function of the newly introduced algorithm, which finds the available key slots
> to be programmed(UFS Host controller Inline Encryption engine has multiple keyslots), program the key slot,
> and return the key slot index as return value of the set key function.
> 3. When read/write operation happens, crypt_map() function in dm-crypt validates whether there is associated
> key configuration index for the request. The Bio will be submitted directly in this case only with the associated
> crypto context.
> 4. Block device driver, eg. UFS host controller driver will create the Transfer requests as per this crypto context and
> encryption happens inside the controller.
Why isn't this all controlled by the ufs drivers, using helpers as
required?
Also why do we even need this API over just implementing TCG
Opal/Opalite on the device?
next prev parent reply other threads:[~2018-06-01 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e9120efc-1e25-79c8-6132-9062dd030539@synopsys.com>
2018-05-28 16:32 ` [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt Milan Broz
2018-05-30 14:52 ` Ladvine D Almeida
2018-06-01 7:52 ` Milan Broz
2018-06-01 8:16 ` Christoph Hellwig [this message]
2018-06-06 10:04 ` Ladvine D Almeida
2018-06-06 13:15 ` Christoph Hellwig
2018-06-01 14:46 ` [dm-devel] " Eric Biggers
2018-06-04 13:15 ` Ladvine D Almeida
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=20180601081642.GA25973@infradead.org \
--to=hch@infradead.org \
--cc=Joao.Pinto@synopsys.com \
--cc=Ladvine.DAlmeida@synopsys.com \
--cc=Manjunath.MB@synopsys.com \
--cc=Prabu.T@synopsys.com \
--cc=Tejas.Joglekar@synopsys.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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).