From: Christoph Hellwig <hch@infradead.org>
To: Ladvine D Almeida <Ladvine.DAlmeida@synopsys.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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>,
"tytso@mit.edu" <tytso@mit.edu>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
Date: Wed, 6 Jun 2018 06:15:15 -0700 [thread overview]
Message-ID: <20180606131515.GB12737@infradead.org> (raw)
In-Reply-To: <BD7FB879CC136E419544C8E2AE7B9C3020C5D6@IN01WEMBXA.internal.synopsys.com>
On Wed, Jun 06, 2018 at 10:04:14AM +0000, Ladvine D Almeida wrote:
> The idea is to make use of the existing utilities like dmsetup to configure the keys, mapping etc.
So fix the utilities to support your encryption instead of implementing
kernel-level shim code.
> TCG Opal/Opalite is FDE solution. right?
Doesn't have to the full disk, although that is the typical use case.
next prev parent reply other threads:[~2018-06-06 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:01 [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt Ladvine D Almeida
2018-05-28 16:32 ` Milan Broz
2018-05-30 14:52 ` Ladvine D Almeida
2018-06-01 7:52 ` Milan Broz
2018-06-01 8:16 ` Christoph Hellwig
2018-06-06 10:04 ` Ladvine D Almeida
2018-06-06 10:04 ` Ladvine D Almeida
2018-06-06 13:15 ` Christoph Hellwig [this message]
2018-06-01 14:46 ` [dm-devel] " Eric Biggers
2018-06-04 13:15 ` Ladvine D Almeida
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=20180606131515.GB12737@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=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.