From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, fdmanana@kernel.org
Subject: [PATCH v4 00/10] btrfs: functional test cases for tempfsid
Date: Thu, 29 Feb 2024 07:19:17 +0530 [thread overview]
Message-ID: <cover.1709162170.git.anand.jain@oracle.com> (raw)
v4: Do not optimize calling _require_..() due to duplicates at the
testcase level.
Fix the failure of btrfs/315 due to changes in the mount command
error output.
btrfs/312 remove unused ret and drop args check in now local func
create_cloned_devices.
v3: Mainly, move the prerequisite checks
_require_btrfs_command inspect-internal dump-super
_require_btrfs_mkfs_uuid_option
to the common/btrfs function mkfs_clone() and move
_require_btrfs_command inspect-internal dump-super
to check_fsid() from each individual testcase.
A few more changes as in each individual testcase.
v2: Each individual patch has undergone numerous fixes based on the
feedback received. Please refer to the individual patches.
This patch set validates the tempfsid feature in Btrfs, testing its
functionality and limitations. Also, has one minor bug fix.
Anand Jain (10):
assign SCRATCH_DEV_POOL to an array
btrfs: introduce tempfsid test group
btrfs: create a helper function, check_fsid(), to verify the tempfsid
btrfs: verify that subvolume mounts are unaffected by tempfsid
btrfs: check if cloned device mounts with tempfsid
btrfs: test case prerequisite _require_btrfs_mkfs_uuid_option
btrfs: introduce helper for creating cloned devices with mkfs
btrfs: verify tempfsid clones using mkfs
btrfs: validate send-receive operation with tempfsid.
btrfs: test tempfsid with device add, seed, and balance
common/btrfs | 74 ++++++++++++++++++++++++++++++++++++
common/rc | 18 +++++++--
doc/group-names.txt | 1 +
tests/btrfs/311 | 87 +++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/311.out | 24 ++++++++++++
tests/btrfs/312 | 78 ++++++++++++++++++++++++++++++++++++++
tests/btrfs/312.out | 19 ++++++++++
tests/btrfs/313 | 52 ++++++++++++++++++++++++++
tests/btrfs/313.out | 16 ++++++++
tests/btrfs/314 | 78 ++++++++++++++++++++++++++++++++++++++
tests/btrfs/314.out | 23 ++++++++++++
tests/btrfs/315 | 91 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/315.out | 10 +++++
13 files changed, 567 insertions(+), 4 deletions(-)
create mode 100755 tests/btrfs/311
create mode 100644 tests/btrfs/311.out
create mode 100755 tests/btrfs/312
create mode 100644 tests/btrfs/312.out
create mode 100755 tests/btrfs/313
create mode 100644 tests/btrfs/313.out
create mode 100755 tests/btrfs/314
create mode 100644 tests/btrfs/314.out
create mode 100755 tests/btrfs/315
create mode 100644 tests/btrfs/315.out
--
2.39.3
next reply other threads:[~2024-02-29 1:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 1:49 Anand Jain [this message]
2024-02-29 1:49 ` [PATCH v4 01/10] assign SCRATCH_DEV_POOL to an array Anand Jain
2024-02-29 1:49 ` [PATCH v4 02/10] btrfs: introduce tempfsid test group Anand Jain
2024-02-29 1:49 ` [PATCH v4 03/10] btrfs: create a helper function, check_fsid(), to verify the tempfsid Anand Jain
2024-02-29 1:49 ` [PATCH v4 04/10] btrfs: verify that subvolume mounts are unaffected by tempfsid Anand Jain
2024-02-29 11:32 ` Filipe Manana
2024-02-29 1:49 ` [PATCH v4 05/10] btrfs: check if cloned device mounts with tempfsid Anand Jain
2024-02-29 11:39 ` Filipe Manana
2024-02-29 1:49 ` [PATCH v4 06/10] btrfs: test case prerequisite _require_btrfs_mkfs_uuid_option Anand Jain
2024-02-29 1:49 ` [PATCH v4 07/10] btrfs: introduce helper for creating cloned devices with mkfs Anand Jain
2024-02-29 1:49 ` [PATCH v4 08/10] btrfs: verify tempfsid clones using mkfs Anand Jain
2024-02-29 11:42 ` Filipe Manana
2024-02-29 1:49 ` [PATCH v4 09/10] btrfs: validate send-receive operation with tempfsid Anand Jain
2024-02-29 11:43 ` Filipe Manana
2024-02-29 1:49 ` [PATCH v4 10/10] btrfs: test tempfsid with device add, seed, and balance Anand Jain
2024-02-29 11:44 ` Filipe Manana
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=cover.1709162170.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=fdmanana@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).