From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Keith Busch <keith.busch@wdc.com>, Christoph Hellwig <hch@lst.de>,
dm-devel@lists.linux.dev, Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-xfs@vger.kernel.org,
Carlos Maiolino <cem@kernel.org>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH v3 00/15] Introduce cached report zones
Date: Tue, 4 Nov 2025 15:41:58 +0100 [thread overview]
Message-ID: <20251104144158.GA27416@lst.de> (raw)
In-Reply-To: <20251104013147.913802-1-dlemoal@kernel.org>
I just threw this into my xfstests setup, and it seems this version
is broken somehow. Running on emulated ZNS devices with XFS I get
a lot of failures with warnings like this:
[ 30.068652] XFS (nvme1n1): empty zone 1 has non-zero used counter (0x1).
[ 49.316873] XFS (nvme0n1): empty zone 2 has non-zero used counter (0x10).
so it seems like it's not tracking WPs correctly, probably when using
zone append and unmount/remounting.
next prev parent reply other threads:[~2025-11-04 14:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 1:31 [PATCH v3 00/15] Introduce cached report zones Damien Le Moal
2025-11-04 1:31 ` [PATCH v3 01/15] block: handle zone management operations completions Damien Le Moal
2025-11-04 4:04 ` Chaitanya Kulkarni
2025-11-04 17:53 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 02/15] block: freeze queue when updating zone resources Damien Le Moal
2025-11-04 4:04 ` Chaitanya Kulkarni
2025-11-04 17:56 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 03/15] block: cleanup blkdev_report_zones() Damien Le Moal
2025-11-04 4:04 ` Chaitanya Kulkarni
2025-11-04 1:31 ` [PATCH v3 04/15] block: introduce disk_report_zone() Damien Le Moal
2025-11-04 4:05 ` Chaitanya Kulkarni
2025-11-04 19:39 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 05/15] block: reorganize struct blk_zone_wplug Damien Le Moal
2025-11-04 4:05 ` Chaitanya Kulkarni
2025-11-05 7:02 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 06/15] block: use zone condition to determine conventional zones Damien Le Moal
2025-11-04 4:05 ` Chaitanya Kulkarni
2025-11-05 7:04 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 07/15] block: track zone conditions Damien Le Moal
2025-11-04 4:08 ` Chaitanya Kulkarni
2025-11-05 7:06 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 08/15] block: refactor blkdev_report_zones() code Damien Le Moal
2025-11-04 4:09 ` Chaitanya Kulkarni
2025-11-05 7:07 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 09/15] block: introduce blkdev_get_zone_info() Damien Le Moal
2025-11-04 4:10 ` Chaitanya Kulkarni
2025-11-05 7:09 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 10/15] block: introduce blkdev_report_zones_cached() Damien Le Moal
2025-11-04 4:11 ` Chaitanya Kulkarni
2025-11-05 7:10 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 11/15] block: introduce BLKREPORTZONESV2 ioctl Damien Le Moal
2025-11-04 4:12 ` Chaitanya Kulkarni
2025-11-04 19:00 ` Bart Van Assche
2025-11-04 20:13 ` Damien Le Moal
2025-11-04 20:36 ` Bart Van Assche
2025-11-05 7:11 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 12/15] block: improve zone_wplugs debugfs attribute output Damien Le Moal
2025-11-04 4:13 ` Chaitanya Kulkarni
2025-11-05 7:11 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 13/15] block: add zone write plug condition to debugfs zone_wplugs Damien Le Moal
2025-11-04 4:15 ` Chaitanya Kulkarni
2025-11-04 7:37 ` Johannes Thumshirn
2025-11-05 7:12 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 14/15] btrfs: use blkdev_report_zones_cached() Damien Le Moal
2025-11-05 7:13 ` Hannes Reinecke
2025-11-04 1:31 ` [PATCH v3 15/15] xfs: " Damien Le Moal
2025-11-04 4:15 ` Chaitanya Kulkarni
2025-11-05 7:14 ` Hannes Reinecke
2025-11-04 14:41 ` Christoph Hellwig [this message]
2025-11-04 20:59 ` [PATCH v3 00/15] Introduce cached report zones Damien Le Moal
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=20251104144158.GA27416@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=dsterba@suse.com \
--cc=keith.busch@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.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 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.