Linux block layer
 help / color / mirror / Atom feed
From: Sven-Hendrik Haase <svenstaro@archlinux.org>
To: Keith Busch <kbusch@kernel.org>,
	Sven-Hendrik Haase <svenstaro@archlinux.org>
Cc: 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: Fri, 10 Jul 2026 20:26:46 +0200	[thread overview]
Message-ID: <35646ff9-eea7-4c02-a39e-a13362e70dd6@archlinux.org> (raw)
In-Reply-To: <alE3PqhMQ63lBcWe@kbusch-mbp>


[-- Attachment #1.1: Type: text/plain, Size: 872 bytes --]



On 10.07.26 20:17, 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/

Oh, indeed. That's the very same patch. Well, looks like it's in the 
queue, then.

Sorry for the noise. :)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2026-07-10 18:26 UTC|newest]

Thread overview: 3+ 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 [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=35646ff9-eea7-4c02-a39e-a13362e70dd6@archlinux.org \
    --to=svenstaro@archlinux.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --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 \
    /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