All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: zlang@kernel.org
Cc: fstests@vger.kernel.org,
	Linux BTRFS Development <linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] fstests: btrfs changes for for-next v2024.01.10
Date: Wed, 10 Jan 2024 05:59:43 +0530	[thread overview]
Message-ID: <eb9b3fa6-a78e-4191-09c6-a37d344bccb1@oracle.com> (raw)

Zorro,

Please pull this branch containing test cases for RST and snapshot 
delete. Thx.


The following changes since commit 17324dbc7743902aec349d12ccad91b3cb6005c5:

   fstests: btrfs: use proper filter for subvolume deletion (2023-12-24 
03:14:21 +0800)

are available in the Git repository at:

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

for you to fetch changes up to e50e5d97b2a217564f27bdebbe1e358eb93653d0:

   btrfs: test snapshotting a deleted subvolume (2024-01-10 04:39:02 +0530)

----------------------------------------------------------------
Anand Jain (1):
       common: add _filter_trailing_whitespace

Johannes Thumshirn (9):
       fstests: doc: add new raid-stripe-tree group
       common: add _require_btrfs_no_nodatacow helper
       common: add _require_btrfs_free_space_tree
       common: add filter for btrfs raid-stripe dump
       btrfs: add fstest for stripe-tree metadata with 4k write
       btrfs: add fstest for 8k write spanning two stripes on 
raid-stripe-tree
       btrfs: add fstest for writing to a file at an offset with RST
       btrfs: add fstests to write 128k to a RST filesystem
       btrfs: add fstest for overwriting a file partially with RST

Omar Sandoval (1):
       btrfs: test snapshotting a deleted subvolume

  .gitignore                         |   1 +
  common/btrfs                       |  17 ++++++++++++
  common/filter                      |   5 ++++
  common/filter.btrfs                |  15 ++++++++++
  doc/group-names.txt                |   1 +
  src/Makefile                       |   2 +-
  src/t_snapshot_deleted_subvolume.c | 102 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/304                    |  58 
+++++++++++++++++++++++++++++++++++++++
  tests/btrfs/304.out                |  58 
+++++++++++++++++++++++++++++++++++++++
  tests/btrfs/305                    |  63 
++++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/305.out                |  82 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/306                    |  61 
+++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/306.out                |  75 
++++++++++++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/307                    |  58 
+++++++++++++++++++++++++++++++++++++++
  tests/btrfs/307.out                |  65 
+++++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/308                    |  62 
+++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/308.out                | 106 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  tests/btrfs/309                    |  27 ++++++++++++++++++
  tests/btrfs/309.out                |   2 ++
  19 files changed, 859 insertions(+), 1 deletion(-)
  create mode 100644 src/t_snapshot_deleted_subvolume.c
  create mode 100755 tests/btrfs/304
  create mode 100644 tests/btrfs/304.out
  create mode 100755 tests/btrfs/305
  create mode 100644 tests/btrfs/305.out
  create mode 100755 tests/btrfs/306
  create mode 100644 tests/btrfs/306.out
  create mode 100755 tests/btrfs/307
  create mode 100644 tests/btrfs/307.out
  create mode 100755 tests/btrfs/308
  create mode 100644 tests/btrfs/308.out
  create mode 100755 tests/btrfs/309
  create mode 100644 tests/btrfs/309.out



                 reply	other threads:[~2024-01-10  0:30 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=eb9b3fa6-a78e-4191-09c6-a37d344bccb1@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.