From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com, fstests@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs/301: test fixes for squotas vs other features
Date: Mon, 20 Nov 2023 13:10:53 -0800 [thread overview]
Message-ID: <cover.1700514431.git.boris@bur.io> (raw)
The squotas targeting tests in btrfs/301 do not currently pass test runs
with compression enabled or free space tree disabled. We can fix the no
free space tree case by querying subvolid rather than assuming
256,257,etc.. Skip compression, it is covered anyway by fsck on the rest
of the tests.
---
V2:
- fix tons of mistakes from global subvid/snapid variables by making
them local
- handle the nested subvol too
- fix descriptions from previous confusion about noholes
- run with and without free space tree
Boris Burkov (2):
btrfs/301: fix hardcoded subvolids
btrfs/301: require_no_compress
tests/btrfs/301 | 172 +++++++++++++++++++++++++++++-------------------
1 file changed, 104 insertions(+), 68 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-20 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 21:10 Boris Burkov [this message]
2023-11-20 21:10 ` [PATCH v2 1/2] btrfs/301: fix hardcoded subvolids Boris Burkov
2023-11-21 10:48 ` Filipe Manana
2023-11-20 21:10 ` [PATCH v2 2/2] btrfs/301: require_no_compress Boris Burkov
2023-11-21 10:50 ` 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.1700514431.git.boris@bur.io \
--to=boris@bur.io \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox