From: Qu Wenruo <wqu@suse.com>
To: Tito Duarte <duartito@gmail.com>, linux-btrfs@vger.kernel.org
Cc: fsverity@lists.linux.dev
Subject: Re: btrfs: spurious fs-verity "FILE CORRUPTED" with large data folios (v7.2+)
Date: Sat, 10 Oct 2026 19:32:29 +1030 [thread overview]
Message-ID: <f180671b-ce45-4bd8-b536-b936ade0a79e@suse.com> (raw)
In-Reply-To: <20261010083827.27604-1-duartito@gmail.com>
在 2026/10/10 19:08, Tito Duarte 写道:
> Hi,
>
> Since v7.2, reading fs-verity files on btrfs intermittently logs fs-verity
> verification failures although the data is intact:
Next time let your agent to check the mailing list first:
https://lore.kernel.org/linux-btrfs/15f4ef9f50e1f4af375e45cf976717041f1a96d4.1791613764.git.wqu@suse.com/
prev parent reply other threads:[~2026-10-10 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 8:38 btrfs: spurious fs-verity "FILE CORRUPTED" with large data folios (v7.2+) Tito Duarte
2026-10-10 9:02 ` 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=f180671b-ce45-4bd8-b536-b936ade0a79e@suse.com \
--to=wqu@suse.com \
--cc=duartito@gmail.com \
--cc=fsverity@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox