From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Christoph Hellwig <hch@lst.de>,
Naohiro Aota <naohiro.aota@wdc.com>,
linux-btrfs@vger.kernel.org,
Hans Holmberg <hans.holmberg@wdc.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [PATCH v5 3/3] generic: basic smoke for filesystems on zoned block devices
Date: Mon, 20 Oct 2025 09:28:19 +0200 [thread overview]
Message-ID: <20251020072818.GA28882@lst.de> (raw)
In-Reply-To: <20251017185633.pvpapg5gq47s2vmm@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Sat, Oct 18, 2025 at 02:56:33AM +0800, Zorro Lang wrote:
> Does this mean the current FSTYP doesn't support zoned?
>
> As this's a generic test case, the FSTYP can be any other filesystems, likes
> nfs, cifs, overlay, exfat, tmpfs and so on, can we create zloop on any of them?
> If not, how about _notrun if current FSTYP doesn't support.
We don't know, and it will be different based on the kernel version.
That being sayd, we should check for a block backed file system
probably.
prev parent reply other threads:[~2025-10-20 7:28 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
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 [this message]
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=20251020072818.GA28882@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--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