FSTests Archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, fstests@vger.kernel.org
Subject: Re: [PATCH 0/5] Btrfs fstests fixups and updates
Date: Sun, 24 Mar 2024 14:05:35 +0530	[thread overview]
Message-ID: <a44ba535-0316-4d1a-9b57-1ea2963af9c8@oracle.com> (raw)
In-Reply-To: <cover.1710871719.git.dsterba@suse.com>

On 3/19/24 23:41, David Sterba wrote:
> Hi,
> 
> a few more fixup from our repository.  They have been in our CI branch
> and consider them tested and working for our needs. All of them are
> btrfs-specific and will not affect other filesystems.
> 
> Please apply, thanks.
> 


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


Except for these two patches, the rest have been applied for the PR.
{
>    generic/733: disable for btrfs > Josef Bacik (3):
>    common/verity: use the correct options for btrfs-corrupt-block}

Thanks, Anand

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



>   common/btrfs        | 10 +++++++++
>   common/rc           |  4 ++--
>   common/verity       |  2 +-
>   tests/btrfs/131     |  2 ++
>   tests/btrfs/172     |  3 +++
>   tests/btrfs/206     |  3 +++
>   tests/btrfs/330     | 54 +++++++++++++++++++++++++++++++++++++++++++++
>   tests/btrfs/330.out |  6 +++++
>   tests/generic/733   |  2 +-
>   9 files changed, 82 insertions(+), 4 deletions(-)
>   create mode 100755 tests/btrfs/330
>   create mode 100644 tests/btrfs/330.out
> 


      parent reply	other threads:[~2024-03-24  8:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 18:11 [PATCH 0/5] Btrfs fstests fixups and updates David Sterba
2024-03-19 18:12 ` [PATCH 1/5] common/verity: use the correct options for btrfs-corrupt-block David Sterba
2024-03-20  9:58   ` Anand Jain
2024-03-20 15:23     ` David Sterba
2024-03-24  7:56       ` Anand Jain
2024-03-19 18:12 ` [PATCH 2/5] btrfs/131,btrfs/172,btrfs/206: add check for block-group-tree feature in btrfs David Sterba
2024-03-20 10:01   ` Anand Jain
2024-03-19 18:12 ` [PATCH 3/5] btrfs/330: add test to validate ro/rw subvol mounting David Sterba
2024-03-20 11:33   ` Anand Jain
2024-03-20 17:01     ` Filipe Manana
2024-03-21  3:51       ` Anand Jain
2024-03-19 18:12 ` [PATCH 4/5] common/rc: use proper temporary file path in _repair_test_fs() David Sterba
2024-03-20 11:35   ` Anand Jain
2024-03-19 18:12 ` [PATCH 5/5] generic/733: disable for btrfs David Sterba
2024-03-19 21:01   ` Christoph Hellwig
2024-03-19 21:10     ` Darrick J. Wong
2024-03-19 21:16       ` Christoph Hellwig
2024-03-20 15:58     ` David Sterba
2024-03-21 21:36       ` Christoph Hellwig
2024-03-21 21:52         ` Kent Overstreet
2024-03-22 15:08           ` Josef Bacik
2024-03-22 15:45             ` Darrick J. Wong
2024-03-22 18:28             ` Kent Overstreet
2024-03-20  9:49 ` [PATCH 0/5] Btrfs fstests fixups and updates Anand Jain
2024-03-20 15:26   ` David Sterba
2024-03-21  4:09 ` [PATCH] common/btrfs: set BTRFS_CORRUPT_BLOCK_OPT_<VALUE|OFFSET> Anand Jain
2024-03-21 11:13   ` Filipe Manana
2024-03-21 12:34     ` Anand Jain
2024-03-24  8:35 ` Anand Jain [this message]

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=a44ba535-0316-4d1a-9b57-1ea2963af9c8@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.com \
    --cc=fstests@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).