From: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
To: fstests@vger.kernel.org
Cc: Prabhakar Pujeri <prabhakar.pujeri@dell.com>,
Zorro Lang <zlang@kernel.org>, Qu Wenruo <wqu@suse.com>,
quwenruo.btrfs@gmx.com, Anand Jain <asj@kernel.org>,
Filipe Manana <fdmanana@suse.com>,
linux-btrfs@vger.kernel.org
Subject: [PATCH v3 4/6] btrfs/333: require scratch before checking encoded reads
Date: Tue, 15 Sep 2026 14:17:43 +0000 [thread overview]
Message-ID: <20260915141745.4299-5-prabhakar.pujeri@dell.com> (raw)
In-Reply-To: <20260915141745.4299-1-prabhakar.pujeri@dell.com>
_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.
Reviewed-by: Qu Wenruo <wqu@suse.com>
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 a75fbf1c..ccac8626 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
--
2.55.0
next prev parent reply other threads:[~2026-09-15 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 14:17 [PATCH v3 0/6] xfstests: add missing _require_scratch checks Prabhakar Pujeri
2026-09-15 14:17 ` [PATCH v3 1/6] generic/590,735: add missing _require_scratch check Prabhakar Pujeri
2026-09-15 14:17 ` [PATCH v3 2/6] generic/795: " Prabhakar Pujeri
2026-09-15 16:54 ` Zorro Lang
2026-09-15 14:17 ` [PATCH v3 3/6] f2fs/015,016: add missing _require_scratch checks Prabhakar Pujeri
2026-09-15 14:17 ` Prabhakar Pujeri [this message]
2026-09-15 14:17 ` [PATCH v3 5/6] btrfs/273: add missing _require_scratch check Prabhakar Pujeri
2026-09-15 14:17 ` [PATCH v3 6/6] overlay/081: " Prabhakar Pujeri
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=20260915141745.4299-5-prabhakar.pujeri@dell.com \
--to=prabhakar.pujeri@dell.com \
--cc=asj@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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