public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com, fstests@vger.kernel.org
Subject: [PATCH 0/2] btrfs/301: test fixes for squotas vs other features
Date: Mon, 20 Nov 2023 10:45:01 -0800	[thread overview]
Message-ID: <cover.1700505679.git.boris@bur.io> (raw)

the squotas targeting tests in btrfs/301 do not currently pass test runs
with noholes and compression enabled. Noholes can be fixed relatively
easily. Skip compression, it is covered anyway by fsck on the rest of
the tests.

Boris Burkov (2):
  btrfs/301: fix hardcoded subvolids
  btrfs/301: require_no_compress

 tests/btrfs/301 | 139 +++++++++++++++++++++++++-----------------------
 1 file changed, 71 insertions(+), 68 deletions(-)

-- 
2.42.0


             reply	other threads:[~2023-11-20 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 18:45 Boris Burkov [this message]
2023-11-20 18:45 ` [PATCH 1/2] btrfs/301: fix hardcoded subvolids Boris Burkov
2023-11-20 19:45   ` Filipe Manana
2023-11-20 19:53     ` Boris Burkov
2023-11-20 18:45 ` [PATCH 2/2] btrfs/301: require_no_compress Boris Burkov

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.1700505679.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