From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 0/2] fstests: btrfs: make space cache related tests future proof
Date: Fri, 26 Dec 2025 08:45:51 +1030 [thread overview]
Message-ID: <20251225221553.19254-1-wqu@suse.com> (raw)
The existing btrfs/131 is testing no space cache, v1 space cache and v2
space cache mount options.
It's fine for LTS kernels as they will stay there for a long time with
v1 space cache support.
However v1 space cache is already deprecated since commit 1e7bec1f7d65
("btrfs: emit a warning about space cache v1 being deprecated"), and the
kernel support for v1 cache will drop soon.
In that case btrfs/131 will cause false alerts, and we will have no test
case covering no space cache and v2 space cache mount options.
The series will:
- Enhance btrfs/131 to skip the test if the kernel has no v1 cache support
This is done by a more explicit check.
- Add a new test case without v1 cache
The newer one can cover cases which is not covered before, including:
* bs > ps cases
* bs < ps cases
* zoned devices
Qu Wenruo (2):
fstests: btrfs/131: add explicit v1 space cache requirement
fstests: btrfs: add a new test case that is future-proof
common/btrfs | 25 +++++++++++
tests/btrfs/131 | 12 +++---
tests/btrfs/340 | 103 ++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/340.out | 15 +++++++
4 files changed, 148 insertions(+), 7 deletions(-)
create mode 100755 tests/btrfs/340
create mode 100644 tests/btrfs/340.out
--
2.51.2
next reply other threads:[~2025-12-25 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 22:15 Qu Wenruo [this message]
2025-12-25 22:15 ` [PATCH 1/2] fstests: btrfs/131: add explicit v1 space cache requirement Qu Wenruo
2026-01-18 18:30 ` Zorro Lang
2025-12-25 22:15 ` [PATCH 2/2] fstests: btrfs: add a new test case that is future-proof Qu Wenruo
2026-01-18 18:31 ` Zorro Lang
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=20251225221553.19254-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