FS/XFS testing framework
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH] btrfs/294: reject zoned devices for now
Date: Mon, 24 Jul 2023 11:04:23 +0800	[thread overview]
Message-ID: <20230724030423.92390-1-wqu@suse.com> (raw)

The test case itself is utilizing RAID5/6, which is not yet supported on
zoned device.

In the future we would use raid-stripe-tree (RST) feature, but for now
just reject zoned devices completely.

And since we're here, also update the _fixed_by_kernel_commit lines, as
the proper fix is already merged upstream.

Signed-off-by: Qu Wenruo <wqu@suse.com>
---
 tests/btrfs/294 | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/tests/btrfs/294 b/tests/btrfs/294
index 61ce7d97..d7d13646 100755
--- a/tests/btrfs/294
+++ b/tests/btrfs/294
@@ -16,11 +16,15 @@ _begin_fstest auto raid volume
 
 # Modify as appropriate.
 _supported_fs btrfs
+
+# No zoned support for RAID56 yet.
+_require_non_zoned_device "${SCRATCH_DEV}"
+
 _require_scratch_dev_pool 8
 _fixed_by_kernel_commit a7299a18a179 \
 	"btrfs: fix u32 overflows when left shifting @stripe_nr"
-_fixed_by_kernel_commit xxxxxxxxxxxx \
-	"btrfs: use a dedicated helper to convert stripe_nr to offset"
+_fixed_by_kernel_commit cb091225a538 \
+	"btrfs: fix remaining u32 overflows when left shifting stripe_nr"
 
 _scratch_dev_pool_get 8
 
-- 
2.41.0


             reply	other threads:[~2023-07-24  3:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  3:04 Qu Wenruo [this message]
2023-07-24  4:55 ` [PATCH] btrfs/294: reject zoned devices for now Zorro Lang
2023-07-24  6:19   ` Naohiro Aota
2023-07-24 14:10 ` Christoph Hellwig
2023-07-25  0:22   ` Naohiro Aota
2023-07-25  0:58     ` Qu Wenruo
2023-07-25 16:11       ` David Sterba
2023-07-27 15:50 ` Zorro Lang
2023-07-27 22:15   ` Qu Wenruo

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=20230724030423.92390-1-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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