Linux block layer
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Linlin Zhang <linlin.zhang@oss.qualcomm.com>
Cc: linux-block@vger.kernel.org, ebiggers@kernel.org,
	gmazyland@gmail.com,  bmarzins@redhat.com,
	linux-kernel@vger.kernel.org, adrianvovk@gmail.com,
	 dm-devel@lists.linux.dev, quic_mdalam@quicinc.com,
	israelr@nvidia.com,  hch@infradead.org, axboe@kernel.dk
Subject: Re: [PATCH v3 0/3] dm-inlinecrypt: add target for inline block device encryption
Date: Wed, 6 May 2026 17:53:54 +0200 (CEST)	[thread overview]
Message-ID: <eca4a1af-0573-b27b-572d-043ded687b05@redhat.com> (raw)
In-Reply-To: <20260430095244.3352446-1-linlin.zhang@oss.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

I committed the patches, thanks.

Mikulas



On Thu, 30 Apr 2026, Linlin Zhang wrote:

> This patch series is based on Eric�s work posted at:
> https://lore.kernel.org/all/ecbb7ea8-11f6-30c1-ad77-bd984c52ca33@quicinc.com/
> 
> Eric�s patches introduce a new dm target, dm-inlinecrypt, to support inline
> block-device encryption. The implementation builds on the work previously done
> in Android�s dm-default-key, but intentionally drops passthrough support,
> as that functionality does not appear likely to be accepted upstream in the
> near future. With this limitation, dm-inlinecrypt is positioned as a
> practical replacement for dm-crypt, rather than a general passthrough
> mechanism.
> 
> On top of Eric�s series, keyring key support is added in dm-inlinecrypt. Thus,
> both keyring key and hex key are feasible for dm-inlinecrypt. In addition,
> dm-inlinecrypt.rst is added as the user-guide of dm-inlinecrypt.
> 
> V2:
> https://lore.kernel.org/all/20260410134031.2880675-1-linlin.zhang@oss.qualcomm.com/
> 
> V1:
> https://lore.kernel.org/all/20260304121729.1532469-1-linlin.zhang@oss.qualcomm.com/
> 
> Eric Biggers (2):
>   block: export blk-crypto symbols required by dm-inlinecrypt
>   dm-inlinecrypt: add target for inline block device encryption
> 
> Linlin Zhang (1):
>   dm: add documentation for dm-inlinecrypt target
> 
>  .../device-mapper/dm-inlinecrypt.rst          | 123 ++++
>  block/blk-crypto.c                            |   3 +
>  drivers/md/Kconfig                            |  11 +
>  drivers/md/Makefile                           |   1 +
>  drivers/md/dm-inlinecrypt.c                   | 596 ++++++++++++++++++
>  5 files changed, 734 insertions(+)
>  create mode 100644 Documentation/admin-guide/device-mapper/dm-inlinecrypt.rst
>  create mode 100644 drivers/md/dm-inlinecrypt.c
> 
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2026-05-06 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  9:52 [PATCH v3 0/3] dm-inlinecrypt: add target for inline block device encryption Linlin Zhang
2026-04-30  9:52 ` [PATCH v3 1/3] block: export blk-crypto symbols required by dm-inlinecrypt Linlin Zhang
2026-04-30  9:52 ` [PATCH v3 2/3] dm-inlinecrypt: add target for inline block device encryption Linlin Zhang
2026-04-30  9:52 ` [PATCH v3 3/3] dm: add documentation for dm-inlinecrypt target Linlin Zhang
2026-05-06 15:53 ` 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=eca4a1af-0573-b27b-572d-043ded687b05@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=adrianvovk@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bmarzins@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=ebiggers@kernel.org \
    --cc=gmazyland@gmail.com \
    --cc=hch@infradead.org \
    --cc=israelr@nvidia.com \
    --cc=linlin.zhang@oss.qualcomm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_mdalam@quicinc.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