From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, josef@toxicpanda.com
Subject: [PATCH 0/3] fstests: btrfs validate sysfs fsid and usage
Date: Wed, 20 Oct 2021 15:16:41 +0800 [thread overview]
Message-ID: <cover.1634713680.git.anand.jain@oracle.com> (raw)
Patch 1 adds a helper to check if the kernel is latest enough to provide
the fsid from the sysfs.
Patch 2 validates the sysfs fsid against the fsid from the sb
Patch 3 is a test case to make sure if the btrfs filesystem usage is
successful on a sprout filesystem with a seed device missing.
Anand Jain (3):
common/btrfs: add _require_btrfs_sysfs_fsid helper
btrfs/248: validate sysfs fsid
btrfs/249: test btrfs filesystem usage command on missing seed device
common/btrfs | 14 ++++++++++
tests/btrfs/248 | 66 ++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/248.out | 2 ++
tests/btrfs/249 | 67 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/249.out | 2 ++
5 files changed, 151 insertions(+)
create mode 100755 tests/btrfs/248
create mode 100644 tests/btrfs/248.out
create mode 100755 tests/btrfs/249
create mode 100644 tests/btrfs/249.out
--
2.27.0
next reply other threads:[~2021-10-20 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 7:16 Anand Jain [this message]
2021-10-20 7:16 ` [PATCH 1/3] common/btrfs: add _require_btrfs_sysfs_fsid helper Anand Jain
2021-10-20 7:16 ` [PATCH 2/3] btrfs/248: validate sysfs fsid Anand Jain
2021-10-20 7:16 ` [PATCH 3/3] btrfs/249: test btrfs filesystem usage command on missing seed device Anand Jain
2021-10-20 13:53 ` Josef Bacik
2021-10-20 14:58 ` Anand Jain
2021-10-20 18:44 ` Josef Bacik
2021-10-20 18:45 ` [PATCH 0/3] fstests: btrfs validate sysfs fsid and usage Josef Bacik
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.1634713680.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.