From: Christoph Hellwig <hch@infradead.org>
To: Adrian Vovk <adrianvovk@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Linlin Zhang <linlin.zhang@oss.qualcomm.com>,
linux-block@vger.kernel.org, ebiggers@kernel.org,
linux-kernel@vger.kernel.org, dm-devel@lists.linux.dev,
quic_mdalam@quicinc.com, gmazyland@gmail.com, israelr@nvidia.com,
mpatocka@redhat.com
Subject: Re: [PATCH v1 0/3] dm-inlinecrypt: add target for inline block device encryption
Date: Thu, 5 Mar 2026 06:38:20 -0800 [thread overview]
Message-ID: <aamVXAqlWGcPXCDe@infradead.org> (raw)
In-Reply-To: <CAAdYy_mSB4U39Onwa=V2e2XB0sJXV6tCGkzwV2-z7ZtMcm+8zg@mail.gmail.com>
On Wed, Mar 04, 2026 at 01:02:41PM -0500, Adrian Vovk wrote:
> Hello Christoph,
>
> Maybe I am misunderstanding something, but this seems orthogonal to
> fscrypt? Userspace would use this to do LUKS full-disk encryption, but with
> the hardware acceleration provided by the inline encryption hardware.
Ok, if people really still want to do that that should be ok.
next prev parent reply other threads:[~2026-03-05 14:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 12:17 [PATCH v1 0/3] dm-inlinecrypt: add target for inline block device encryption Linlin Zhang
2026-03-04 12:17 ` [PATCH v1 1/3] block: export blk-crypto symbols required by dm-inlinecrypt Linlin Zhang
2026-03-09 14:01 ` Mikulas Patocka
2026-03-09 15:05 ` Jens Axboe
2026-03-09 16:12 ` Mikulas Patocka
2026-03-04 12:17 ` [PATCH v1 2/3] dm-inlinecrypt: add target for inline block device encryption Linlin Zhang
2026-03-04 13:11 ` Milan Broz
2026-03-25 11:27 ` Linlin Zhang
2026-03-12 7:01 ` Eric Biggers
2026-03-13 13:25 ` Mikulas Patocka
2026-03-13 15:27 ` Milan Broz
2026-03-25 11:57 ` Linlin Zhang
2026-03-25 15:07 ` Milan Broz
2026-03-25 6:55 ` Linlin Zhang
2026-03-04 12:17 ` [PATCH v1 3/3] dm-inlinecrypt: Expose inline crypto caps to the device Linlin Zhang
2026-03-12 6:35 ` Eric Biggers
2026-03-13 13:19 ` Mikulas Patocka
2026-03-25 6:38 ` Linlin Zhang
2026-03-04 13:06 ` [PATCH v1 0/3] dm-inlinecrypt: add target for inline block device encryption Christoph Hellwig
2026-03-04 18:09 ` Adrian Vovk
[not found] ` <CAAdYy_mSB4U39Onwa=V2e2XB0sJXV6tCGkzwV2-z7ZtMcm+8zg@mail.gmail.com>
2026-03-05 14:38 ` Christoph Hellwig [this message]
2026-03-25 7:04 ` 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=aamVXAqlWGcPXCDe@infradead.org \
--to=hch@infradead.org \
--cc=adrianvovk@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=israelr@nvidia.com \
--cc=linlin.zhang@oss.qualcomm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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