From: Israel Rukshin <email@example.com>
To: Milan Broz <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>
Cc: Max Gurtovoy <firstname.lastname@example.org>,
dm-devel <email@example.com>, Nitzan Carmi <firstname.lastname@example.org>,
Eric Biggers <email@example.com>
Subject: Re: [dm-devel] [RFC PATCH 0/1] Add inline encryption support for dm-crypt
Date: Mon, 17 Jan 2022 16:00:59 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 1/17/2022 12:50 PM, Milan Broz wrote:
> On 17/01/2022 08:52, Christoph Hellwig wrote:
>> On Fri, Jan 14, 2022 at 09:51:20PM +0100, Milan Broz wrote:
>>> I think dm-crypt should stay as SW crypto only (using kernel crypto
>>> so HW acceleration is done through crypto drivers there).
>>> A cleaner solution is to write a much simpler new dm-crypt-inline
>>> which will implement only inline encryption.
>>> (And userspace can decide which target to use.)
>>> Code should be just an extension to the dm-linear target, most
>>> of dm-crypt complexity is not needed here.
>> Why do we even need a dm target for this as well? There should be no
>> need to clone or remap bios, so I think hamdling inline crypto should be
>> just a small addition to the core block layer.
> Well, yes, that was my question too :-)
> Maybe there is need to have some new userspace utility to configure that
> but otherwise I think that for inline encryption device mapper layer
> only increases complexity and reduces IO performance.
Regarding performance degradation, I added only one if condition at the
data path (inside #ifdef).
> Could anyone elaborate what it the reason for such DM extension?
> Compatibility with existing encryption/key management tools (like LUKS)?
> Easy support in LVM? ...
DM extension gives us several capabilities:
1. Use the Linux keyring and other key management tools.
- I used "keyctl padd user test-key @u < /tmp/wrapped_dek" at my tests
2. Split a single block device into several DMs. Allow us to use a
different encryption key and encryption mode per DM.
3. Replace a key during I/O by using "dmsetup suspend /dev/dm-0" and
"dmsetup resume /dev/dm-0".
dm-devel mailing list
next prev parent reply other threads:[~2022-01-17 14:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 18:09 [dm-devel] [RFC PATCH 0/1] Add inline encryption support for dm-crypt Israel Rukshin
2022-01-13 18:09 ` [dm-devel] [PATCH 1/1] dm crypt: Add inline encryption support Israel Rukshin
2022-01-14 8:06 ` Damien Le Moal
2022-01-14 8:14 ` Damien Le Moal
2022-01-16 10:29 ` Israel Rukshin
2022-01-13 21:22 ` [dm-devel] [RFC PATCH 0/1] Add inline encryption support for dm-crypt Bart Van Assche
2022-01-14 20:51 ` Milan Broz
2022-01-14 22:27 ` Eric Biggers
2022-01-15 9:22 ` Milan Broz
2022-01-18 19:38 ` Eric Biggers
2022-01-19 5:18 ` Christoph Hellwig
2022-01-17 7:52 ` Christoph Hellwig
2022-01-17 10:50 ` Milan Broz
2022-01-17 14:00 ` Israel Rukshin [this message]
2022-01-18 16:45 ` Christoph Hellwig
2022-01-18 20:27 ` Eric Biggers
2022-01-19 5:15 ` Christoph Hellwig
2022-01-14 22:49 ` Eric Biggers
2022-01-16 10:15 ` Israel Rukshin
2022-01-18 20:02 ` Eric Biggers
2022-01-19 15:45 ` Israel Rukshin
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.