From: Linlin Zhang <linlin.zhang@oss.qualcomm.com>
To: Mikulas Patocka <mpatocka@redhat.com>,
Eric Biggers <ebiggers@kernel.org>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Benjamin Marzinski <bmarzins@redhat.com>,
Neeraj Soni <neeraj.soni@oss.qualcomm.com>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] dm-inlinecrypt: add support for hardware-wrapped keys
Date: Sat, 16 May 2026 04:50:44 -0700 [thread overview]
Message-ID: <20260516115045.3958326-1-linlin.zhang@oss.qualcomm.com> (raw)
dm-inlinecrypt currently assumes that all keys are raw software keys.
That does not work for platforms where inline encryption expects
hardware-wrapped key material managed by secure firmware/hardware.
This series adds support for hardware-wrapped keys in dm-inlinecrypt by
introducing an explicit <is_wrappedkey> target argument. The flag lets
dm-inlinecrypt select the proper blk-crypto key type at key
initialization time:
- 0: BLK_CRYPTO_KEY_TYPE_RAW
- 1: BLK_CRYPTO_KEY_TYPE_HW_WRAPPED
With this change, dm-inlinecrypt can support both raw and wrapped key
deployment models without hardcoding one key ownership model.
The series also:
- updates target argument parsing to include the new required flag
- propagates the wrapped/raw state in target status output
- updates dm-inlinecrypt documentation and examples accordingly
Note: this extends target syntax by adding one required parameter, so
existing userspace table definitions must be updated.
dm-inlinecrypt currently assumes that all keys are raw software keys.
That does not work for platforms where inline encryption expects
hardware-wrapped key material managed by secure firmware/hardware.
This series adds support for hardware-wrapped keys in dm-inlinecrypt by
introducing an explicit <is_wrappedkey> target argument. The flag lets
dm-inlinecrypt select the proper blk-crypto key type at key
initialization time:
- 0: BLK_CRYPTO_KEY_TYPE_RAW
- 1: BLK_CRYPTO_KEY_TYPE_HW_WRAPPED
With this change, dm-inlinecrypt can support both raw and wrapped key
deployment models without hardcoding one key ownership model.
The series also:
- updates target argument parsing to include the new required flag
- propagates the wrapped/raw state in target status output
- updates dm-inlinecrypt documentation and examples accordingly
Note: this extends target syntax by adding one required parameter, so
existing userspace table definitions must be updated.
Linlin Zhang (1):
dm-inlinecrypt: add support for hardware-wrapped keys
.../device-mapper/dm-inlinecrypt.rst | 10 ++-
drivers/md/dm-inlinecrypt.c | 71 +++++++++++--------
2 files changed, 50 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2026-05-16 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 11:50 Linlin Zhang [this message]
2026-05-16 11:50 ` [PATCH v2 1/1] " Linlin Zhang
2026-05-16 12:17 ` Milan Broz
2026-05-18 8:11 ` Linlin Zhang
2026-05-18 12:37 ` Mikulas Patocka
2026-05-22 5:56 ` Linlin Zhang
2026-05-18 12:49 ` Milan Broz
2026-05-22 5:57 ` Linlin Zhang
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=20260516115045.3958326-1-linlin.zhang@oss.qualcomm.com \
--to=linlin.zhang@oss.qualcomm.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=snitzer@kernel.org \
/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
all inboxes | Powered by JetHome®