From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: fix the overly strict chunk type check on dump-tree
Date: Fri, 29 May 2026 19:06:16 +0930 [thread overview]
Message-ID: <cover.1780047275.git.wqu@suse.com> (raw)
Commit 408e45feb325 ("btrfs-progs: dump-tree: add extra chunk type
checks") introduced a chunk type check before dumping the tree.
However it's too strict as I'm a total idiot, and forgot to we still
need to dump chunk tree blocks.
Fix it and add a regression test.
Qu Wenruo (2):
btrfs-progs: dump-tree: fix the chunk type check for system chunks
btrfs-progs: misc-tests: add a regression test case for dump tree
cmds/inspect-dump-tree.c | 5 ++--
.../072-dump-tree-chunk-bytenr/test.sh | 25 +++++++++++++++++++
2 files changed, 28 insertions(+), 2 deletions(-)
create mode 100755 tests/misc-tests/072-dump-tree-chunk-bytenr/test.sh
--
2.54.0
next reply other threads:[~2026-05-29 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 9:36 Qu Wenruo [this message]
2026-05-29 9:36 ` [PATCH 1/2] btrfs-progs: dump-tree: fix the chunk type check for system chunks Qu Wenruo
2026-05-29 9:36 ` [PATCH 2/2] btrfs-progs: misc-tests: add a regression test case for dump tree 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.1780047275.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