From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Prabhakar Pujeri <prabhakar.pujeri@dell.com>, fstests@vger.kernel.org
Cc: Zorro Lang <zlang@kernel.org>, Anand Jain <asj@kernel.org>,
Filipe Manana <fdmanana@suse.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs/333: require scratch before checking encoded reads
Date: Wed, 2 Sep 2026 14:45:29 +0930 [thread overview]
Message-ID: <5115a152-295f-4744-8080-e0d2ecdeb360@gmx.com> (raw)
In-Reply-To: <20260902033310.1698-1-prabhakar.pujeri@dell.com>
在 2026/9/2 13:03, Prabhakar Pujeri 写道:
> _require_btrfs_iouring_encoded_read() formats and mounts the scratch
> device while checking for encoded-read support. Without a configured
> scratch device, callers therefore fail inside the helper before any
> scratch requirement is checked.
>
> Add _require_scratch at the top of the helper so that all of its
> callers skip cleanly when no scratch device is present.
>
> Changes in v2:
> - Move _require_scratch into _require_btrfs_iouring_encoded_read() so
> the requirement is enforced for all callers of the helper, per Qu
> Wenruo's suggestion. Revert the v1 caller-side change in btrfs/333.
> - Cc Qu Wenruo.
>
> v1: https://lore.kernel.org/fstests/20260831104200.2269-1-prabhakar.pujeri@dell.com/
Change log should be put after the "---" line.
Otherwise looks good to me.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
>
> Signed-off-by: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
> ---
> common/btrfs | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/common/btrfs b/common/btrfs
> index a75fbf1..ccac862 100644
> --- a/common/btrfs
> +++ b/common/btrfs
> @@ -1055,6 +1055,7 @@ _require_btrfs_iouring_encoded_read()
> local tmpfile
> local ret
>
> + _require_scratch
> _require_command src/btrfs_encoded_read
>
> _scratch_mkfs &> /dev/null
prev parent reply other threads:[~2026-09-02 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 3:33 [PATCH v2] btrfs/333: require scratch before checking encoded reads Prabhakar Pujeri
2026-09-02 5:15 ` Qu Wenruo [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=5115a152-295f-4744-8080-e0d2ecdeb360@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--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=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox