From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dm-devel@lists.linux.dev, hch@lst.de, brauner@kernel.org,
djwong@kernel.org, viro@zeniv.linux.org.uk,
regressions@lists.linux.dev, torvalds@linux-foundation.org
Subject: Re: [PATCH RESEND 0/5] block: validate direct I/O memory alignment
Date: Thu, 30 Jul 2026 13:26:26 +0200 [thread overview]
Message-ID: <20260730112626.GA24827@lst.de> (raw)
In-Reply-To: <ampce7mxSmxAwAiu@kbusch-mbp>
On Wed, Jul 29, 2026 at 02:03:07PM -0600, Keith Busch wrote:
> > > Hi Jens, have you had a chance to look at this one yet? This addresses
> > > previous issues with certain device mappers under direct io.
> >
> > I they look fine, but at this point we should toss them into 7.3. Yes
> > I know there are regressions around this, but from 6.1x days. And the
> > series doesn't apply to the current block-7.2 anyway.
>
> This series is kind of old at this point, but yes, it's not fixing a new
> regression either. I'm okay if this goes to the next window, and I will
> handle the stable follow-up.
Honestly, I think that'a a reall bad idea. This is a regression in 6.18,
and while it took a while for people to hit this with their a little
more complicated lvm/md setups, it has stopped real systems from being
used. We need to fix this ASAP.
next prev parent reply other threads:[~2026-07-30 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 20:10 [PATCH RESEND 0/5] block: validate direct I/O memory alignment Keith Busch
2026-07-20 20:10 ` [PATCH RESEND 1/5] block: use blkdev_iov_iter_get_pages status for errors Keith Busch
2026-07-20 20:10 ` [PATCH RESEND 2/5] block: fix dio leak on metadata mapping error Keith Busch
2026-07-20 20:10 ` [PATCH RESEND 3/5] loop: set dma_alignment from the backing file for direct I/O Keith Busch
2026-07-20 20:10 ` [PATCH RESEND 4/5] zloop: set dma_alignment from the backing files " Keith Busch
2026-07-20 20:10 ` [PATCH RESEND 5/5] block: validate user space vectors during extraction Keith Busch
2026-07-29 19:15 ` [PATCH RESEND 0/5] block: validate direct I/O memory alignment Keith Busch
2026-07-29 19:18 ` Jens Axboe
2026-07-29 20:03 ` Keith Busch
2026-07-29 23:34 ` Jens Axboe
2026-07-30 11:26 ` Christoph Hellwig [this message]
2026-07-30 12:52 ` Keith Busch
2026-07-30 13:25 ` Thorsten Leemhuis
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=20260730112626.GA24827@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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 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.