From: Christoph Hellwig <hch@lst.de>
To: cem@kernel.org
Cc: aalbersh@redhat.com, linux-xfs@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH] mkfs: fix zone capacity check for sequential zones
Date: Wed, 12 Nov 2025 13:50:56 +0100 [thread overview]
Message-ID: <20251112125056.GA27028@lst.de> (raw)
In-Reply-To: <20251112123356.701593-1-cem@kernel.org>
On Wed, Nov 12, 2025 at 01:33:16PM +0100, cem@kernel.org wrote:
> FWIS, writing the patch description I'm assuming that the conventional zones
> always come first and we can't have a zoned device starting with
> sequential zones followed by conventional zones.
XFS kinda assumes this by not counting counting conventional zones found
after sequential zones, so we'll error out due to the lack of conventional
space later unless a separate device is used.
> +static void
> +zone_validate_capacity(
> + struct zone_info *zi,
> + __u64 capacity,
> + bool conventional)
> +{
> + if (conventional && (zi->zone_capacity != zi->zone_size)) {
No need for the inner braces.
Otherwise this looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
Note that we should also verify that if a device is used purely as
RT device (aka no internal RT device), that there are either no
conventional zones, or zone capacity == zone_size. I can look into
that as an incremental patch.
next prev parent reply other threads:[~2025-11-12 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 12:33 [PATCH] mkfs: fix zone capacity check for sequential zones cem
2025-11-12 12:50 ` Christoph Hellwig [this message]
2025-11-12 13:25 ` Carlos Maiolino
2025-11-12 14:36 ` Christoph Hellwig
2025-11-12 15:02 ` Carlos Maiolino
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=20251112125056.GA27028@lst.de \
--to=hch@lst.de \
--cc=aalbersh@redhat.com \
--cc=cem@kernel.org \
--cc=linux-xfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox