From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs-progs: check: Add repair support for mismatch dir item hash
Date: Thu, 25 Oct 2018 15:44:45 +0800 [thread overview]
Message-ID: <20181025074449.32469-1-wqu@suse.com> (raw)
This patchset can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/repair_bad_dir_item_hash
This is still based on the latest stable v4.17.1 branch (which is already a
little old now)
We have report from suse bugzilla where user report latest kernel refuse
to mount the fs.
The problem turns out to be that some old kernel (around Jan 2017) has a
bug that could leads to corrupted dir item with mismatch hash.
This patchset will allow btrfs check --repair to repair such problem.
Qu Wenruo (4):
btrfs-progs: lowmem check: Add ability to repair dir item with
mismatch hash
btrfs-progs: original check: Use mismatch_dir_hash_record to record
bad dir items
btrfs-progs: original check: Add ability to repair dir item with
invalid hash
btrfs-progs: fsck-tests: Make 026-bad-dir-item-name test case to
verify if btrfs-check can also repair it
check/main.c | 121 +++++++++++++++++-
check/mode-common.c | 51 ++++++++
check/mode-common.h | 5 +-
check/mode-lowmem.c | 46 ++++++-
check/mode-lowmem.h | 1 +
check/mode-original.h | 14 ++
ctree.h | 3 +
dir-item.c | 6 +-
.../026-bad-dir-item-name/description.txt | 41 ++++++
.../fsck-tests/026-bad-dir-item-name/test.sh | 13 --
10 files changed, 272 insertions(+), 29 deletions(-)
create mode 100644 tests/fsck-tests/026-bad-dir-item-name/description.txt
delete mode 100755 tests/fsck-tests/026-bad-dir-item-name/test.sh
--
2.19.1
next reply other threads:[~2018-10-25 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 7:44 Qu Wenruo [this message]
2018-10-25 7:44 ` [PATCH 1/4] btrfs-progs: lowmem check: Add ability to repair dir item with mismatch hash Qu Wenruo
2018-10-25 7:44 ` [PATCH 2/4] btrfs-progs: original check: Use mismatch_dir_hash_record to record bad dir items Qu Wenruo
2018-10-25 7:44 ` [PATCH 3/4] btrfs-progs: original check: Add ability to repair dir item with invalid hash Qu Wenruo
2018-10-25 7:44 ` [PATCH 4/4] btrfs-progs: fsck-tests: Make 026-bad-dir-item-name test case to verify if btrfs-check can also repair it Qu Wenruo
2019-01-07 6:51 ` [PATCH 0/4] btrfs-progs: check: Add repair support for mismatch dir item hash Qu Wenruo
2019-01-07 6:53 ` 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=20181025074449.32469-1-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;
as well as URLs for NNTP newsgroup(s).