From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: check/lowmem: fix false alerts about verity items
Date: Wed, 25 Mar 2026 10:17:51 +1030 [thread overview]
Message-ID: <cover.1774395991.git.wqu@suse.com> (raw)
Leo reported and fixed a bug in original mode where false alerts were
triggered about verity items.
Unfortunately we have a similar problem in lowmem mode too.
Fix the lowmem mode false alert and add a test case to prevent similar
problems in the future.
Qu Wenruo (2):
btrfs-progs: check/lowmem: recognize verity item keys
btrfs-progs: fsck-tests: add a test case for verity items
check/mode-lowmem.c | 3 +++
.../fsck-tests/072-verity-items/fsverity.img.xz | Bin 0 -> 2364 bytes
tests/fsck-tests/072-verity-items/test.sh | 15 +++++++++++++++
3 files changed, 18 insertions(+)
create mode 100644 tests/fsck-tests/072-verity-items/fsverity.img.xz
create mode 100755 tests/fsck-tests/072-verity-items/test.sh
--
2.53.0
next reply other threads:[~2026-03-24 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 23:47 Qu Wenruo [this message]
2026-03-24 23:47 ` [PATCH 1/2] btrfs-progs: check/lowmem: recognize verity item keys Qu Wenruo
2026-03-24 23:47 ` [PATCH 2/2] btrfs-progs: fsck-tests: add a test case for verity items 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=cover.1774395991.git.wqu@suse.com \
--to=wqu@suse.com \
--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