From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: tune: fix the leftover csum change item and add a test case for it
Date: Tue, 23 May 2023 08:37:11 +0800 [thread overview]
Message-ID: <cover.1684802060.git.wqu@suse.com> (raw)
David's cyclic csum change tests exposed a bug even with the latest csum
change code, that I'm a total idiot and forgot to delete the csum change
item.
This results a bug that if we have run multiple csum changes to the same
target csum type (e.g. CRC32C->SHA256->CRC32C->SHA256), the second
conversion to the same type would fail due to the left over csum change items.
This series would do the fix and add a test case to cover this bug.
Qu Wenruo (2):
btrfs-progs: tune: delete the csum change item after converting the fs
btrfs-progs: tests/misc: add a test case for csum change
.../058-btrfstune-csum-change/test.sh | 26 ++++++++++++
tune/change-csum.c | 42 +++++++++++++++++--
2 files changed, 64 insertions(+), 4 deletions(-)
create mode 100755 tests/misc-tests/058-btrfstune-csum-change/test.sh
--
2.40.1
next reply other threads:[~2023-05-23 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 0:37 Qu Wenruo [this message]
2023-05-23 0:37 ` [PATCH 1/2] btrfs-progs: tune: delete the csum change item after converting the fs Qu Wenruo
2023-05-23 0:37 ` [PATCH 2/2] btrfs-progs: tests/misc: add a test case for csum change Qu Wenruo
2023-05-23 10:46 ` [PATCH 0/2] btrfs-progs: tune: fix the leftover csum change item and add a test case for it David Sterba
2023-05-23 11:00 ` 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.1684802060.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