From: Damien Le Moal <dlemoal@kernel.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>,
Naohiro Aota <naohiro.aota@wdc.com>, Qu Wenruo <wqu@suse.com>,
Mark Korenberg <socketpair@gmail.com>,
Dongjiang Zhu <zhudongjiang@fygo.io>
Subject: Re: [PATCH 1/4] btrfs-progs: zoned: use cached zone reports if available
Date: Tue, 17 Nov 2026 03:59:03 -0800 [thread overview]
Message-ID: <c1398625-3a6e-4fa8-a021-bffdfa32ceb0@kernel.org> (raw)
In-Reply-To: <20261117084948.3848762-2-johannes.thumshirn@wdc.com>
On 11/17/26 00:49, Johannes Thumshirn wrote:
> Since Linux 6.19, BLKREPORTZONEV2 with BLK_ZONE_REP_CACHED reports zones
> from the kernel's cached zone information instead of asking the device.
> Use it when the headers and the kernel support it, fall back to
> BLKREPORTZONE otherwise.
>
> Cached reports return open and closed zones as BLK_ZONE_COND_ACTIVE,
> handle it where open or closed zones are counted, and provide a fallback
> definition for older headers.
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Looks OK to me.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-11-17 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 8:49 [PATCH 0/4] btrfs-progs: zoned: detect and repair FS with exhausted active zones Johannes Thumshirn
2026-11-17 8:49 ` [PATCH 1/4] btrfs-progs: zoned: use cached zone reports if available Johannes Thumshirn
2026-11-17 11:59 ` Damien Le Moal [this message]
2026-11-17 8:49 ` [PATCH 2/4] btrfs-progs: zoned: add btrfs_finish_dev_zone() Johannes Thumshirn
2026-11-17 11:59 ` Damien Le Moal
2026-11-17 8:49 ` [PATCH 3/4] btrfs-progs: zoned: add btrfs_get_max_active_zones() Johannes Thumshirn
2026-11-17 12:03 ` Damien Le Moal
2026-11-17 8:49 ` [PATCH 4/4] btrfs-progs: check: detect and repair exhausted zoned active zones Johannes Thumshirn
2026-11-18 7:40 ` Qu Wenruo
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=c1398625-3a6e-4fa8-a021-bffdfa32ceb0@kernel.org \
--to=dlemoal@kernel.org \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=socketpair@gmail.com \
--cc=wqu@suse.com \
--cc=zhudongjiang@fygo.io \
/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.