From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
Keith Busch <kbusch@kernel.org>,
Christop Hellwig <hch@infradead.org>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/3] Fix bio splitting in the crypto fallback code
Date: Wed, 25 Jun 2025 16:42:56 -0700 [thread overview]
Message-ID: <20250625234259.1985366-1-bvanassche@acm.org> (raw)
Hi Jens,
When using the crypto fallback code, large bios are split twice. A first
time by bio_split_to_limits() and a second time by the crypto fallback
code. Additionally, this causes bios not to be submitted in LBA error and
hence triggers write errors for zoned block devices. This patch series
fixes this by splitting bios once. Please consider this patch series for
the next merge window.
Thanks,
Bart.
Bart Van Assche (3):
block: Split blk_crypto_fallback_split_bio_if_needed()
block: Introduce the BLK_FEAT_CALLS_BIO_SPLIT_TO_LIMITS flag
block: Rework splitting of encrypted bios
block/bio.c | 3 +++
block/blk-core.c | 19 ++++++++-----
block/blk-crypto-fallback.c | 53 ++++++++++++++++++++-----------------
block/blk-crypto-internal.h | 7 +++++
block/blk-crypto.c | 3 ++-
block/blk-merge.c | 13 +++++++--
block/blk-mq.c | 3 ++-
block/blk.h | 9 +++++++
include/linux/blk_types.h | 1 +
include/linux/blkdev.h | 6 ++++-
10 files changed, 81 insertions(+), 36 deletions(-)
next reply other threads:[~2025-06-25 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 23:42 Bart Van Assche [this message]
2025-06-25 23:42 ` [PATCH 1/3] block: Split blk_crypto_fallback_split_bio_if_needed() Bart Van Assche
2025-06-25 23:42 ` [PATCH 2/3] block: Introduce the BLK_FEAT_CALLS_BIO_SPLIT_TO_LIMITS flag Bart Van Assche
2025-06-26 5:24 ` Christop Hellwig
2025-06-25 23:42 ` [PATCH 3/3] block: Rework splitting of encrypted bios Bart Van Assche
2025-06-26 5:28 ` Christop Hellwig
2025-07-10 18:04 ` Bart Van Assche
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=20250625234259.1985366-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=ebiggers@google.com \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-block@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.