From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Carlos Maiolino <cem@kernel.org>
Cc: "zlang@kernel.org" <zlang@kernel.org>, hch <hch@lst.de>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] xfs: Add test for mkfs with smaller zone capacity
Date: Mon, 24 Nov 2025 17:31:03 +0000 [thread overview]
Message-ID: <becfce20-3948-40db-bdb5-7dc64438da26@wdc.com> (raw)
In-Reply-To: <ba3tbnjq2dernii2n6leyc6z76lcezsjemomtm54mrbm2xcnz5@kx3qp3qgrtqe>
On 11/24/25 4:27 PM, Carlos Maiolino wrote:
> On Fri, Nov 21, 2025 at 06:51:31AM +0000, Johannes Thumshirn wrote:
>> On 11/20/25 5:09 PM, cem@kernel.org wrote:
>>> From: Carlos Maiolino <cem@kernel.org>
>>>
>>> Add a regression test for initializing zoned block devices with
>>> sequential zones with a capacity smaller than the conventional
>>> zones capacity.
>>
>> Hi Carlos,
>>
>> Two quick questions:
>>
>> 1) Is there a specific reason this is a xfs only test? I think checking
>> this on btrfs and f2fs would make sense as well, like with generic/781.
> I wrote this mostly as a regression test for xfs's mkfs, but yeah, I don't
> think there is any reason for this to be xfs-specific.
>
>> 2) I would also mount the FS and perform some IO on it.
> I'm not sure about this. Do you have any purpose in mind? This is
> specifically to test mkfs is able to properly format the filesystem, not
> to try the kernel module per-se.
> One could argue that something 'could' go wrong in the mkfs that might
> be found out only via some IO, but that would require much more than
> just 'some IO'.
Yep that's what I had in mind.
> I do think a mount/unmount might add some value to the test, but I fail
> to see why issuing a random amount of I/O would prove the correctness of
> mkfs properly dealing with small capacities.
fstests does a fsck after each test, doesn't it? So that should be
sufficient as well.
next prev parent reply other threads:[~2025-11-24 17:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 16:08 [PATCH 0/2] xfs: add regression test for small zone capacity cem
2025-11-20 16:08 ` [PATCH 1/2] common/zoned: enable passing a custom capacity cem
2025-11-21 6:46 ` Johannes Thumshirn
2025-11-21 6:50 ` Christoph Hellwig
2025-11-22 7:41 ` Zorro Lang
2025-11-20 16:08 ` [PATCH 2/2] xfs: Add test for mkfs with smaller zone capacity cem
2025-11-21 6:51 ` Christoph Hellwig
2025-11-21 6:51 ` Johannes Thumshirn
2025-11-21 6:57 ` hch
2025-11-21 7:00 ` Johannes Thumshirn
2025-11-21 8:34 ` Hans Holmberg
2025-11-24 15:27 ` Carlos Maiolino
2025-11-24 17:31 ` Johannes Thumshirn [this message]
2025-11-24 17:34 ` hch
2025-11-25 13:01 ` Carlos Maiolino
2025-11-22 8:36 ` Zorro Lang
2025-11-24 16:04 ` Carlos Maiolino
2025-11-20 23:15 ` [PATCH] common/rc: fix _xfs_is_realtime_file for internal rt devices Darrick J. Wong
2025-11-20 23:24 ` Darrick J. Wong
2025-11-21 6:47 ` Christoph Hellwig
2025-11-21 16:20 ` Darrick J. Wong
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=becfce20-3948-40db-bdb5-7dc64438da26@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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