From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, z1281552865@gmail.com, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: fix aligning of bounced dio read bios
Date: Mon, 13 Jul 2026 09:39:01 -0600 [thread overview]
Message-ID: <alUGlVDWkZNyUE4N@kbusch-mbp> (raw)
In-Reply-To: <20260713152912.2333321-1-hch@lst.de>
On Mon, Jul 13, 2026 at 05:29:11PM +0200, Christoph Hellwig wrote:
> bio_iov_iter_align_down expects the "normal" biovec layout from vector 0,
> while bio_iov_iter_bounce_read abuses vector 0 for a bounce buffer
> allocation. Pass an explicit bvec to bio_iov_iter_align_down to deal
> with this case to avoid a double unpin.
Can you instead just have bio_iov_iter_bounce_read() align down the size
it extracts rather than letting it over-extract and reverting the excess?
next prev parent reply other threads:[~2026-07-13 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 15:29 [PATCH] block: fix aligning of bounced dio read bios Christoph Hellwig
2026-07-13 15:39 ` Keith Busch [this message]
2026-07-13 15:44 ` Keith Busch
2026-07-13 15:54 ` Christoph Hellwig
2026-07-14 6:10 ` [syzbot ci] " syzbot ci
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=alUGlVDWkZNyUE4N@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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