All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
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: Sat, 24 Feb 2024 21:42:42 +0800	[thread overview]
Message-ID: <20240224214241.840F.409509F4@e16-tech.com> (raw)
In-Reply-To: <20240222095048.14211-1-dsterba@suse.com>

Hi,

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

On linux 6.8-rc5+, generic/733 with btrfs filesystem have some chance(>50%) to
success now.  Is this expected?

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/02/24

> CC: Josef Bacik <josef@toxicpanda.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>  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
> 



  parent reply	other threads:[~2024-02-24 13:42 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
2024-02-24 13:42 ` Wang Yugui [this message]
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=20240224214241.840F.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --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.