From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: [GIT PULL] fstests: btrfs changes for for-next staged-20250328
Date: Fri, 28 Mar 2025 09:26:24 +0800 [thread overview]
Message-ID: <20250328012637.23744-1-anand.jain@oracle.com> (raw)
Zorro,
Please pull this branch, which includes test cases for sysfs syntax
verification of btrfs read policy and chunk size. v4 has been on the
mailing list for a month now, along with fix from Filipe and Zoned
testcase from Johannes.
Please note that the commit:
"fstests: btrfs: zoned: verify RAID conversion with write pointer mismatch"
has the changes discussed with Naohiro, including his review-by tag,
(which is missing in your patches-in-queue branch).
Test case number for above commit is changed to btrfs/335 following
the integration of the sysfs patches.
Thank you.
The following changes since commit d71157da4ef4cfdbf39e2c4a07f8013633e6bcbe:
common/rc: explicitly test for engine availability in _require_fio (2025-03-17 00:43:12 +0800)
are available in the Git repository at:
https://github.com/asj/fstests/tree/staged-20250328
for you to fetch changes up to 208a7f874df38bf873137d00634783422965a7ab:
fstests: btrfs: zoned: verify RAID conversion with write pointer mismatch (2025-03-28 08:25:55 +0800)
----------------------------------------------------------------
Anand Jain (5):
fstests: common/rc: set_fs_sysfs_attr: redirect errors to stdout
fstests: filter: helper for sysfs error filtering
fstests: common/rc: add sysfs argument verification helpers
fstests: btrfs: testcase for sysfs policy syntax verification
fstests: btrfs: testcase for sysfs chunk_size attribute validation
Filipe Manana (1):
btrfs/058: fix test to actually have an open tmpfile during the send operation
Johannes Thumshirn (1):
fstests: btrfs: zoned: verify RAID conversion with write pointer mismatch
common/filter | 9 ++++
common/rc | 3 +-
common/sysfs | 142 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/058 | 28 +++++++++--
tests/btrfs/329 | 19 +++++++
tests/btrfs/329.out | 19 +++++++
tests/btrfs/334 | 19 +++++++
tests/btrfs/334.out | 14 ++++++
tests/btrfs/335 | 62 +++++++++++++++++++++++
tests/btrfs/335.out | 7 +++
10 files changed, 317 insertions(+), 5 deletions(-)
create mode 100644 common/sysfs
create mode 100755 tests/btrfs/329
create mode 100644 tests/btrfs/329.out
create mode 100755 tests/btrfs/334
create mode 100644 tests/btrfs/334.out
create mode 100755 tests/btrfs/335
create mode 100644 tests/btrfs/335.out
next reply other threads:[~2025-03-28 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 1:26 Anand Jain [this message]
2025-03-28 2:03 ` [GIT PULL] fstests: btrfs changes for for-next staged-20250328 Zorro Lang
2025-03-28 2:53 ` Anand Jain
2025-03-28 18:02 ` David Sterba
2025-04-04 6:11 ` Christoph Hellwig
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=20250328012637.23744-1-anand.jain@oracle.com \
--to=anand.jain@oracle.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