From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: new tests for zoned xfs
Date: Thu, 1 May 2025 14:55:53 -0700 [thread overview]
Message-ID: <20250501215553.GI25675@frogsfrogsfrogs> (raw)
In-Reply-To: <20250501134302.2881773-1-hch@lst.de>
On Thu, May 01, 2025 at 08:42:37AM -0500, Christoph Hellwig wrote:
> Hi all,
>
> this series adds the various new tests for zoned xfs, including testing
> data placement.
The first 14 patches I think I've already been running for a few weeks
against software/hardware zoned support and haven't seen many problems.
I will have a few fixups to apply after this, though.
So for patches 1-14,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
(Will go look at #15 separately)
--D
prev parent reply other threads:[~2025-05-01 21:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 13:42 new tests for zoned xfs Christoph Hellwig
2025-05-01 13:42 ` [PATCH 01/15] xfs: add a zoned growfs test Christoph Hellwig
2025-05-01 13:42 ` [PATCH 02/15] xfs: add a test for zoned block accounting after remount Christoph Hellwig
2025-05-06 19:32 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 03/15] xfs: add test to check for block layer reordering Christoph Hellwig
2025-05-01 13:42 ` [PATCH 04/15] xfs: add a test to check that data growfs fails with internal rt device Christoph Hellwig
2025-05-06 19:35 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 05/15] add a new rw_hint helper Christoph Hellwig
2025-05-01 13:42 ` [PATCH 06/15] xfs: add a test for write lifetime hints Christoph Hellwig
2025-05-06 19:42 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 07/15] xfs: add a test for writeback after close Christoph Hellwig
2025-05-06 19:45 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 08/15] xfs: test zone stream separation for two direct writers Christoph Hellwig
2025-05-06 19:52 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 09/15] xfs: test zone stream separation for two buffered writers Christoph Hellwig
2025-05-06 19:54 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 10/15] xfs: test zoned ENOSPC behavior with multiple writers Christoph Hellwig
2025-05-06 19:58 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 11/15] xfs: test zoned GC file defragmentation for sequential writers Christoph Hellwig
2025-05-06 20:00 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 12/15] xfs: test zoned GC file defragmentation for random writers Christoph Hellwig
2025-05-06 20:01 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 13/15] xfs: test that xfs_repair does not mess up the zone used counter Christoph Hellwig
2025-05-01 13:42 ` [PATCH 14/15] xfs: test that truncate does not spuriously return ENOSPC Christoph Hellwig
2025-05-06 20:06 ` Zorro Lang
2025-05-01 13:42 ` [PATCH 15/15] xfs: test that we can handle spurious zone wp advancements Christoph Hellwig
2025-05-02 16:04 ` Darrick J. Wong
2025-05-05 13:01 ` Hans Holmberg
2025-05-05 9:51 ` [PATCH v2 " Hans Holmberg
2025-05-05 15:08 ` Darrick J. Wong
2025-05-06 20:16 ` Zorro Lang
2025-05-07 5:12 ` hch
2025-05-07 6:05 ` Hans Holmberg
2025-05-01 21:55 ` Darrick J. Wong [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=20250501215553.GI25675@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hans.holmberg@wdc.com \
--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