[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aRSXQKgkV55fFtNG@fedora>
Date: Wed, 12 Nov 2025 22:18:40 +0800
From: Ming Lei <ming.lei@...hat.com>
To: hch <hch@....de>
Cc: Johannes Thumshirn <Johannes.Thumshirn@....com>,
"Darrick J. Wong" <djwong@...nel.org>, Jan Kara <jack@...e.cz>,
Keith Busch <kbusch@...nel.org>, Dave Chinner <david@...morbit.com>,
Carlos Maiolino <cem@...nel.org>,
Christian Brauner <brauner@...nel.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
Subject: Re: fall back from direct to buffered I/O when stable writes are
required
On Thu, Nov 06, 2025 at 01:49:00PM +0100, hch wrote:
> On Thu, Nov 06, 2025 at 09:50:10AM +0000, Johannes Thumshirn wrote:
> > On 11/5/25 10:44 PM, Darrick J. Wong wrote:
> > > Just out of curiosity -- is qemu itself mutating the buffers that it is
> > > passing down to the lower levels via dio? Or is it a program in the
> > > guest that's mutating buffers that are submitted for dio, which then get
> > > zerocopied all the way down to the hypervisor?
> >
> > If my memory serves me right it is the guest (or at least can be). I
> > remember a bug report on btrfs where a Windows guest had messed up
> > checksums because of modifying inflight I/O.
>
> qemu passes I/O through, so yes it is guest controller. Windows is most
> famous, but the Linux swap code can trigger it easily too.
Looks buffer overwrite is actually done by buggy software in guest side,
why is qemu's trouble? Or will qemu IO emulator write to the IO buffer
when guest IO is inflight?
Thanks,
Ming
Powered by blists - more mailing lists