FSTests Archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, fdmanana@kernel.org
Subject: [GIT PULL] fstests: btrfs changes for for-next v2024.03.24
Date: Sun, 24 Mar 2024 20:15:42 +0530	[thread overview]
Message-ID: <20240324144721.8343-1-anand.jain@oracle.com> (raw)

Zorro,

Some of the patches here were part of a group where other patches might
need revision. However, these patches are ready for integration.

Please pull.

Thank you.

The following changes since commit ec5b77f70e602b2312bd25ac9d6f7c507d47f2a6:

  fstests: add missing commit IDs to some tests (2024-03-13 23:56:38 +0800)

are available in the Git repository at:

  https://github.com/asj/fstests/tree/staged-20240324 

for you to fetch changes up to 805eeea406a7cd78ab76f91cb061bce7e9a3e83c:

  fstests: btrfs/195: skip raid setups not in the profile configs (2024-03-24 19:57:42 +0800)

----------------------------------------------------------------
Anand Jain (2):
      common/btrfs: introduce _require_btrfs_send_version
      generic: test mount fails on physical device with configured dm volume

Boris Burkov (3):
      btrfs/320: skip -O squota runs
      btrfs/277: specify protocol version 3 for verity send
      btrfs/316: use rescan wrapper

David Sterba (1):
      common/rc: use proper temporary file path in _repair_test_fs()

Josef Bacik (3):
      btrfs/131,btrfs/172,btrfs/206: add check for block-group-tree feature in btrfs
      btrfs/330: add test to validate ro/rw subvol mounting
      fstests: btrfs/195: skip raid setups not in the profile configs

 common/btrfs          | 20 +++++++++++++----
 common/rc             |  4 ++--
 tests/btrfs/131       |  2 ++
 tests/btrfs/172       |  3 +++
 tests/btrfs/195       |  8 +++++++
 tests/btrfs/206       |  3 +++
 tests/btrfs/277       |  3 ++-
 tests/btrfs/281       |  2 +-
 tests/btrfs/284       |  2 +-
 tests/btrfs/316       |  3 ++-
 tests/btrfs/320       |  6 ++++--
 tests/btrfs/330       | 53 +++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/330.out   |  6 ++++++
 tests/generic/741     | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/741.out |  3 +++
 15 files changed, 166 insertions(+), 12 deletions(-)
 create mode 100755 tests/btrfs/330
 create mode 100644 tests/btrfs/330.out
 create mode 100755 tests/generic/741
 create mode 100644 tests/generic/741.out

                 reply	other threads:[~2024-03-24 14:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240324144721.8343-1-anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fdmanana@kernel.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).