From: Tito Duarte <duartito@gmail.com>
To: wqu@suse.com
Cc: linux-btrfs@vger.kernel.org, ebiggers@kernel.org, vonbloom@gmail.com
Subject: Re: [PATCH v2] btrfs: fix the fsverity callback where unexpected range is verified
Date: Sat, 10 Oct 2026 10:10:31 +0100 [thread overview]
Message-ID: <20261010091031.41686-1-duartito@gmail.com> (raw)
In-Reply-To: <15f4ef9f50e1f4af375e45cf976717041f1a96d4.1791613764.git.wqu@suse.com>
On Sat, Oct 10, 2026 at 04:59:49PM +1030, Qu Wenruo wrote:
> [FIX]
> Instead of calling fsverity_verify_folio(), call
> fsverity_verify_blocks() to verify only the read range.
Tested on Debian's 7.2.8-1 kernel with this change applied, 4K pages:
- arm64 VM (virtio-blk), the reproducer from my report [1]: from 10
spurious "FILE CORRUPTED" reports per 30 mount/read cycles to 0
(0 in 120 cycles over four runs)
- boots from a composefs root with overlayfs verity=require on btrfs:
arm64 previously 7-10 reports per test run (three boots), now none;
x86_64 with Secure Boot and lockdown also clean
Sorry for the duplicate report, I had missed your patch.
Tested-by: Tito Duarte <duartito@gmail.com>
[1] https://lore.kernel.org/linux-btrfs/20261010083827.27604-1-duartito@gmail.com/
prev parent reply other threads:[~2026-10-10 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 6:29 [PATCH v2] btrfs: fix the fsverity callback where unexpected range is verified Qu Wenruo
2026-10-10 7:50 ` Eric Biggers
2026-10-10 9:10 ` Tito Duarte [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=20261010091031.41686-1-duartito@gmail.com \
--to=duartito@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=vonbloom@gmail.com \
--cc=wqu@suse.com \
/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