From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>, Neptune <z1281552865@gmail.com>,
0wnerD1ed <l7z@0b1t.tech>,
linux-block@vger.kernel.org
Subject: bio bounce buffering fixes v3
Date: Thu, 16 Jul 2026 11:12:44 +0200 [thread overview]
Message-ID: <20260716091306.316625-1-hch@lst.de> (raw)
Hi all,
this series fixes a few issues with the bio bounce buffering code.
Changes since v2:
- fix another issue found by the original reproducer
Changes since v1:
- go back to the previously tested approach without iov_iter.c
changes that break small vectors
Diffstat:
bio.c | 53 +++++++++++++++++++++++++++++------------------------
1 file changed, 29 insertions(+), 24 deletions(-)
next reply other threads:[~2026-07-16 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 9:12 Christoph Hellwig [this message]
2026-07-16 9:12 ` [PATCH 1/2] block: handle huge zero folios in bio_free_folios Christoph Hellwig
2026-07-16 9:12 ` [PATCH 2/2] block: fix aligning of bounced dio read bios Christoph Hellwig
2026-07-16 12:12 ` bio bounce buffering fixes v3 Jens Axboe
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=20260716091306.316625-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=l7z@0b1t.tech \
--cc=linux-block@vger.kernel.org \
--cc=z1281552865@gmail.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