From: Filipe Manana <fdmanana@kernel.org>
To: David Sterba <dsterba@suse.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH] generic/733: disable for btrfs
Date: Thu, 22 Feb 2024 11:34:09 +0000 [thread overview]
Message-ID: <CAL3q7H6myPAEAkfz68pw8e6FS-WDx3j+1GAN1dJ-rQ07YBucmA@mail.gmail.com> (raw)
In-Reply-To: <20240222095048.14211-1-dsterba@suse.com>
On Thu, Feb 22, 2024 at 9:51 AM David Sterba <dsterba@suse.com> wrote:
>
> This tests if a clone source can be read but in btrfs there's an
> exclusive lock and the test always fails. The functionality might be
> implemented in btrfs in the future but for now disable the test.
>
> CC: Josef Bacik <josef@toxicpanda.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Looks good, thanks.
> ---
> tests/generic/733 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/generic/733 b/tests/generic/733
> index d88d92a4705add..b26fa47dad776f 100755
> --- a/tests/generic/733
> +++ b/tests/generic/733
> @@ -18,7 +18,7 @@ _begin_fstest auto clone punch
> . ./common/reflink
>
> # real QA test starts here
> -_supported_fs generic
> +_supported_fs generic ^btrfs
> _require_scratch_reflink
> _require_cp_reflink
> _require_xfs_io_command "fpunch"
> --
> 2.42.1
>
>
next prev parent reply other threads:[~2024-02-22 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:50 [PATCH] generic/733: disable for btrfs David Sterba
2024-02-22 11:34 ` Filipe Manana [this message]
2024-02-24 13:42 ` Wang Yugui
2024-02-26 10:14 ` David Sterba
2024-02-25 15:41 ` Zorro Lang
2024-02-26 11:33 ` David Sterba
2024-02-26 18:07 ` Zorro Lang
2024-04-09 14:49 ` Anand Jain
2024-04-09 14:46 ` David Sterba
2024-04-09 15:01 ` Anand Jain
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=CAL3q7H6myPAEAkfz68pw8e6FS-WDx3j+1GAN1dJ-rQ07YBucmA@mail.gmail.com \
--to=fdmanana@kernel.org \
--cc=dsterba@suse.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.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 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.