From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Sven-Hendrik Haase <svenstaro@archlinux.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
regressions@lists.linux.dev, linux-block@vger.kernel.org,
Li Chen <me@linux.beauty>,
Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [REGRESSION] commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem
Date: Mon, 13 Jul 2026 11:27:47 +0200 [thread overview]
Message-ID: <20260713092747.GB8112@lst.de> (raw)
In-Reply-To: <alE3PqhMQ63lBcWe@kbusch-mbp>
On Fri, Jul 10, 2026 at 12:17:34PM -0600, Keith Busch wrote:
> On Fri, Jul 10, 2026 at 08:07:32PM +0200, Sven-Hendrik Haase wrote:
> > I noticed that starting with Linux 7.1, my pmem volumes inside of QEMU
> > stopped working. My use case is this:
> >
> > qemu-system-x86_64 ... tons of QEMU flags ...
> > -object memory-backend-file,id=pmem0,share=on,merge=on,discard-data=on,mem-path=/path/pmem0.pmem,size=100G
> > -device virtio-pmem-pci,memdev=pmem0,id=nv0
> >
> > This used to work but inside the VM I'd get this when running mkfs.ext4
> > /dev/pmem0 with guest kernel 7.1.3:
>
> This pending fix (which is the same as what you proposed here) should
> take care of it:
>
> https://lore.kernel.org/linux-block/20260709020145.4011533-1-joseph.qi@linux.alibaba.com/
Note that it can stil fail with that alone. The real fix is this:
https://lore.kernel.org/all/20260709124455.1547912-1-joseph.qi@linux.alibaba.com/
prev parent reply other threads:[~2026-07-13 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 18:07 [REGRESSION] commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem Sven-Hendrik Haase
2026-07-10 18:17 ` Keith Busch
2026-07-10 18:26 ` Sven-Hendrik Haase
2026-07-13 9:27 ` Christoph Hellwig [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=20260713092747.GB8112@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=joseph.qi@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=me@linux.beauty \
--cc=regressions@lists.linux.dev \
--cc=svenstaro@archlinux.org \
/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