From: Christoph Hellwig <hch@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] blk-crypto-fallback: Fix deadlock when encrypting large bio in dm layer
Date: Mon, 17 Aug 2026 02:13:48 -0700 [thread overview]
Message-ID: <aoLQzDNH90tdg0Cp@infradead.org> (raw)
In-Reply-To: <20260814194507.GA2644249@google.com>
On Fri, Aug 14, 2026 at 07:45:07PM +0000, Eric Biggers wrote:
> It is what you asked for on v1 and you've now changed your position, as
> far as I can tell.
No, you completely misinterpreted it.
> I can change the Fixes commit to e7f57d2c47e2.
> dm-inlinecrypt is useful and it does not make sense to drop it.
Well, I disagree, and it obviously missed this problem.
prev parent reply other threads:[~2026-08-17 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 22:03 [PATCH v2] blk-crypto-fallback: Fix deadlock when encrypting large bio in dm layer Eric Biggers
2026-08-14 6:34 ` Christoph Hellwig
2026-08-14 19:45 ` Eric Biggers
2026-08-17 9:13 ` Christoph Hellwig [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=aoLQzDNH90tdg0Cp@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=ebiggers@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.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