From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, zlang@redhat.com, fdmanana@kernel.org
Subject: [PATCH v2 0/2] fstests: new test cases for generic group
Date: Sat, 16 Mar 2024 22:32:32 +0530 [thread overview]
Message-ID: <cover.1710599671.git.anand.jain@oracle.com> (raw)
v2: Fixes as per review comments on the individual patches.
Patch 1/2 relocates a tempfsid (clone device) test case from btrfs group
to the generic group.
Patch 2/2 validates a recently discovered and resolved bug in Btrfs;
however, the test case can be made generic.
Anand Jain (2):
shared: move btrfs clone device testcase to the shared group
generic: test mount fails on physical device with configured dm volume
common/rc | 14 +++++++
tests/btrfs/312 | 78 -------------------------------------
tests/btrfs/312.out | 19 ---------
tests/generic/741 | 60 +++++++++++++++++++++++++++++
tests/generic/741.out | 3 ++
tests/shared/001 | 89 +++++++++++++++++++++++++++++++++++++++++++
tests/shared/001.out | 4 ++
7 files changed, 170 insertions(+), 97 deletions(-)
delete mode 100755 tests/btrfs/312
delete mode 100644 tests/btrfs/312.out
create mode 100755 tests/generic/741
create mode 100644 tests/generic/741.out
create mode 100755 tests/shared/001
create mode 100644 tests/shared/001.out
--
2.39.3
next reply other threads:[~2024-03-16 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 17:02 Anand Jain [this message]
2024-03-16 17:02 ` [PATCH v2 1/2] shared: move btrfs clone device testcase to the shared group Anand Jain
2024-03-18 22:02 ` David Sterba
2024-03-18 22:15 ` Christoph Hellwig
2024-03-19 4:16 ` Zorro Lang
2024-03-19 17:17 ` Anand Jain
2024-03-19 17:27 ` David Sterba
2024-03-19 20:43 ` Christoph Hellwig
2024-03-20 16:08 ` David Sterba
2024-03-21 21:41 ` Christoph Hellwig
2024-04-09 14:43 ` Anand Jain
2024-03-16 17:02 ` [PATCH v2 2/2] generic: test mount fails on physical device with configured dm volume Anand Jain
2024-03-24 8:49 ` Anand Jain
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.1710599671.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 \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).