From: hch <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Zorro Lang <zlang@redhat.com>, hch <hch@lst.de>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [PATCH v5 3/3] generic: basic smoke for filesystems on zoned block devices
Date: Wed, 22 Oct 2025 06:32:21 +0200 [thread overview]
Message-ID: <20251022043221.GA2371@lst.de> (raw)
In-Reply-To: <20251021144920.GH3356773@frogsfrogsfrogs>
On Tue, Oct 21, 2025 at 07:49:20AM -0700, Darrick J. Wong wrote:
> Except for zonefs, I think you probably have to try mkfsing the zoned
> block device to decide if the fs really works because the others all had
> zone support added after the initial release.
zonefs isn't support by xfstests because it simply shows a fixed layout
of one file per zone and thus none of the tests would work.
next prev parent reply other threads:[~2025-10-22 4:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 15:20 [PATCH v5 0/3] fstests: basic smoke test on zoned loop device Johannes Thumshirn
2025-10-16 15:20 ` [PATCH v5 1/3] common/zoned: add _require_zloop Johannes Thumshirn
2025-10-16 23:49 ` Naohiro Aota
2025-10-16 15:20 ` [PATCH v5 2/3] common/zoned: add helpers for creation and teardown of zloop devices Johannes Thumshirn
2025-10-16 15:48 ` Darrick J. Wong
2025-10-16 15:50 ` Johannes Thumshirn
2025-10-17 0:44 ` Naohiro Aota
2025-10-17 16:35 ` Darrick J. Wong
2025-10-17 18:38 ` Zorro Lang
2025-10-16 15:20 ` [PATCH v5 3/3] generic: basic smoke for filesystems on zoned block devices Johannes Thumshirn
2025-10-16 15:49 ` Darrick J. Wong
2025-10-16 23:48 ` Naohiro Aota
2025-10-16 23:54 ` Anand Jain
2025-10-17 4:17 ` Christoph Hellwig
2025-10-17 18:56 ` Zorro Lang
2025-10-18 11:13 ` Johannes Thumshirn
2025-10-18 14:05 ` Zorro Lang
2025-10-20 6:21 ` Johannes Thumshirn
2025-10-21 9:33 ` Johannes Thumshirn
2025-10-21 14:49 ` Darrick J. Wong
2025-10-22 4:32 ` hch [this message]
2025-10-22 7:24 ` Zorro Lang
2025-10-22 7:34 ` hch
2025-10-22 4:35 ` hch
2025-10-22 6:27 ` Johannes Thumshirn
2025-10-22 6:33 ` hch
2025-10-20 7:28 ` Christoph Hellwig
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=20251022043221.GA2371@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=cem@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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