From: Mikulas Patocka <mpatocka@redhat.com>
To: Linlin Zhang <linlin.zhang@oss.qualcomm.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Milan Broz <gmazyland@gmail.com>,
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: Re: [PATCH v3 0/1] dm-inlinecrypt: add support for hardware-wrapped keys
Date: Mon, 15 Jun 2026 10:34:46 +0200 (CEST) [thread overview]
Message-ID: <5a1403ea-bec3-f414-c322-5c19edee5bf0@redhat.com> (raw)
In-Reply-To: <13febc50-41b2-479c-97f3-f3eecc648871@oss.qualcomm.com>
On Mon, 15 Jun 2026, Linlin Zhang wrote:
> Hi Milan, Eric and Mikulas,
>
> Do you have a chance to help review this patch?
>
> I'm appreciated if you can help give some comments or accept and help merge this patch.
>
> Thanks,
> Linlin
Hi
I already accepted this patch, I will send it to Linus in this merge
window.
Mikulas
> On 5/25/2026 8:13 PM, Linlin Zhang wrote:
> > 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 optional <key_type> target argument. The flag lets
> > dm-inlinecrypt select the proper blk-crypto key type at key
> > initialization time:
> >
> > - 1: BLK_CRYPTO_KEY_TYPE_RAW
> > - 2: 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
> > Linlin Zhang (1):
> > dm-inlinecrypt: add support for hardware-wrapped keys
> >
> > .../device-mapper/dm-inlinecrypt.rst | 20 +++---
> > drivers/md/dm-inlinecrypt.c | 63 ++++++++++++-------
> > 2 files changed, 54 insertions(+), 29 deletions(-)
> >
>
prev parent reply other threads:[~2026-06-15 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 12:13 Linlin Zhang
2026-05-25 12:13 ` [PATCH v3 1/1] " Linlin Zhang
2026-06-20 21:27 ` Eric Biggers
2026-06-15 5:39 ` [PATCH v3 0/1] " Linlin Zhang
2026-06-15 8:34 ` Mikulas Patocka [this message]
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=5a1403ea-bec3-f414-c322-5c19edee5bf0@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=linlin.zhang@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome