All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
Cc: fstests@vger.kernel.org, Zorro Lang <zlang@kernel.org>,
	Anand Jain <asj@kernel.org>, Filipe Manana <fdmanana@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs/333: require scratch before checking encoded reads
Date: Mon, 31 Aug 2026 10:21:25 -0700	[thread overview]
Message-ID: <20260831172125.GI839663@frogsfrogsfrogs> (raw)
In-Reply-To: <20260831104200.2269-1-prabhakar.pujeri@dell.com>

On Mon, Aug 31, 2026 at 10:42:00AM +0000, Prabhakar Pujeri wrote:
> _require_btrfs_iouring_encoded_read() formats and mounts the scratch
> device while checking for encoded-read support.  Without a configured
> scratch device, the test therefore fails before reaching its existing
> _require_scratch call.
> 
> Move _require_scratch before the encoded-read check so the test is skipped
> before its first scratch operation.
> 
> Signed-off-by: Prabhakar Pujeri <prabhakar.pujeri@dell.com>

That looks right to me,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  tests/btrfs/333 | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/btrfs/333 b/tests/btrfs/333
> index 6214d7c..9dcdf1c 100755
> --- a/tests/btrfs/333
> +++ b/tests/btrfs/333
> @@ -13,6 +13,7 @@ _begin_fstest auto quick compress rw io_uring ioctl
>  
>  _require_command src/btrfs_encoded_read
>  _require_command src/btrfs_encoded_write
> +_require_scratch
>  _require_btrfs_iouring_encoded_read
>  # Encoded writes are reject for inodes with the NODATASUM flag, so we must skip
>  # the test if running with either the nodatasum or nodatacow (which implies
> -- 
> 2.55.0
> 
> 

  reply	other threads:[~2026-08-31 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 10:42 [PATCH] btrfs/333: require scratch before checking encoded reads Prabhakar Pujeri
2026-08-31 17:21 ` Darrick J. Wong [this message]
2026-08-31 23:09 ` Qu Wenruo

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=20260831172125.GI839663@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=asj@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=prabhakar.pujeri@dell.com \
    --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.