Re: [PATCH v3 0/3] dm-inlinecrypt: add target for inline block device encryption

Mikulas Patocka <[email protected]>
Newsgroups dev.linux.lists.dm-devel,org.kernel.vger.linux-block,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
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/[email protected]/
> 
> 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/[email protected]/
> 
> V1:
> https://lore.kernel.org/all/[email protected]/
> 
> 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
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.