Re: [PATCH RESEND 0/5] block: validate direct I/O memory alignment

Keith Busch <[email protected]> Thu, 30 Jul 2026 06:52:28 -0600
Newsgroups dev.linux.lists.dm-devel,dev.linux.lists.regressions,org.kernel.vger.linux-block,org.kernel.vger.linux-fsdevel
Message-ID <amtJDCtczVyX1baB@kbusch-mbp>
On Thu, Jul 30, 2026 at 01:26:26PM +0200, Christoph Hellwig wrote:
> 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.

This should have gone in several weeks ago, IMO. You can most readily
hit a problem running qemu against one of those lvm setups. We're just
so late in this release cycle that I'm not pushing hard for 7.2, but I
would support that choice too.