From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dm-devel@lists.linux.dev, axboe@kernel.dk, brauner@kernel.org,
djwong@kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 0/5] block: validate direct I/O memory alignment
Date: Tue, 14 Jul 2026 13:05:18 -0600 [thread overview]
Message-ID: <alaIbgXtMerwCRk3@kbusch-mbp> (raw)
In-Reply-To: <20260714043543.GA30880@lst.de>
On Tue, Jul 14, 2026 at 06:35:43AM +0200, Christoph Hellwig wrote:
> On Wed, Jun 24, 2026 at 10:09:00AM -0700, Keith Busch wrote:
> > From: Keith Busch <kbusch@kernel.org>
> >
> > This addresses the misaligned direct-io problem behind various threads:
>
> It looks like this never got merged and is still missing in 7.2-rc3.
Yeah, I think this fix is good to go even mid 7.2-rc, but if not, would
be appreciated if we can get it staged for linux-next.
prev parent reply other threads:[~2026-07-14 19:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 17:09 [PATCH v3 0/5] block: validate direct I/O memory alignment Keith Busch
2026-06-24 17:09 ` [PATCH v3 1/5] block: use blkdev_iov_iter_get_pages status for errors Keith Busch
2026-06-25 6:20 ` Hannes Reinecke
2026-06-25 11:56 ` Christoph Hellwig
2026-06-24 17:09 ` [PATCH v3 2/5] block: fix dio leak on metadata mapping error Keith Busch
2026-06-25 6:21 ` Hannes Reinecke
2026-06-24 17:09 ` [PATCH v3 3/5] loop: set dma_alignment from the backing file for direct I/O Keith Busch
2026-06-25 6:25 ` Hannes Reinecke
2026-06-25 11:57 ` Christoph Hellwig
2026-06-24 17:09 ` [PATCH v3 4/5] zloop: set dma_alignment from the backing files " Keith Busch
2026-06-25 6:26 ` Hannes Reinecke
2026-06-25 11:57 ` Christoph Hellwig
2026-06-24 17:09 ` [PATCH v3 5/5] block: validate user space vectors during extraction Keith Busch
2026-06-25 6:28 ` Hannes Reinecke
2026-06-25 11:57 ` Christoph Hellwig
2026-07-14 4:35 ` [PATCH v3 0/5] block: validate direct I/O memory alignment Christoph Hellwig
2026-07-14 19:05 ` Keith Busch [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=alaIbgXtMerwCRk3@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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