From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH 00/11] Lowmem mode btrfs fixes exposed by complex tree
Date: Wed, 22 Nov 2017 17:03:14 +0800 [thread overview]
Message-ID: <20171122090325.29458-1-wqu@suse.com> (raw)
The patchset can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/lowmem_fix
The patchset is mostly rebased to v4.14, since there is some conflicts
with lowmem repair enhancement from Su Yue.
However the lowmem repair enhancement from Su Yue caused one regression,
and the original lowmem code also has some problem handling tree reloc
tree.
The first 2 patches are newly introduced to address this.
The rest are not touched at all (except the conflicts).
As always, the 9th patch may not reach mail list due to its size.
Please use github repo to fetch that file.
Qu Wenruo (11):
btrfs-progs: lowmem check: Fix regression which screws up extent
allocator
btrfs-progs: lowmem check: Fix NULL pointer access caused by large
tree reloc tree
btrfs-progs: lowmem check: Fix inlined data extent ref lookup
btrfs-progs: lowmem check: Fix false backref lost warning for keyed
extent data ref
btrfs-progs: fsck-test: Introduce test case for false data extent
backref lost
btrfs-progs: backref: Allow backref walk to handle direct parent ref
btrfs-progs: lowmem check: Fix function call stack overflow caused by
wrong tree reloc tree detection
btrfs-progs: lowmem check: Fix false alerts for image with shared
block ref only backref
btrfs-progs: fsck-test: Add new image with shared block ref only
metadata backref
btrfs-progs: lowmem check: Fix false alerts of referencer count
mismatch for snapshot
btrfs-progs: fsck-tests: Introduce test case with keyed data backref
with shared tree blocks
backref.c | 3 +
cmds-check.c | 79 +++++++++++++++------
.../020-extent-ref-cases/keyed_data_ref_only.img | Bin 0 -> 4096 bytes
.../keyed_data_ref_with_shared_leaf.img | Bin 0 -> 19456 bytes
.../shared_block_ref_only.raw.xz | Bin 0 -> 217204 bytes
5 files changed, 61 insertions(+), 21 deletions(-)
create mode 100644 tests/fsck-tests/020-extent-ref-cases/keyed_data_ref_only.img
create mode 100644 tests/fsck-tests/020-extent-ref-cases/keyed_data_ref_with_shared_leaf.img
create mode 100644 tests/fsck-tests/020-extent-ref-cases/shared_block_ref_only.raw.xz
--
2.15.0
next reply other threads:[~2017-11-22 9:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 9:03 Qu Wenruo [this message]
2017-11-22 9:03 ` [PATCH 01/11] btrfs-progs: lowmem check: Fix regression which screws up extent allocator Qu Wenruo
2017-11-22 9:03 ` [PATCH 02/11] btrfs-progs: lowmem check: Fix NULL pointer access caused by large tree reloc tree Qu Wenruo
2017-11-22 9:03 ` [PATCH 03/11] btrfs-progs: lowmem check: Fix inlined data extent ref lookup Qu Wenruo
2017-11-22 9:03 ` [PATCH 04/11] btrfs-progs: lowmem check: Fix false backref lost warning for keyed extent data ref Qu Wenruo
2017-11-22 9:03 ` [PATCH 05/11] btrfs-progs: fsck-test: Introduce test case for false data extent backref lost Qu Wenruo
2017-11-22 9:03 ` [PATCH 06/11] btrfs-progs: backref: Allow backref walk to handle direct parent ref Qu Wenruo
2017-11-22 9:03 ` [PATCH 07/11] btrfs-progs: lowmem check: Fix function call stack overflow caused by wrong tree reloc tree detection Qu Wenruo
2017-11-22 9:03 ` [PATCH 08/11] btrfs-progs: lowmem check: Fix false alerts for image with shared block ref only backref Qu Wenruo
2017-11-22 9:03 ` [PATCH 10/11] btrfs-progs: lowmem check: Fix false alerts of referencer count mismatch for snapshot Qu Wenruo
2017-11-22 9:03 ` [PATCH 11/11] btrfs-progs: fsck-tests: Introduce test case with keyed data backref with shared tree blocks Qu Wenruo
2017-11-24 14:46 ` [PATCH 00/11] Lowmem mode btrfs fixes exposed by complex tree David Sterba
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=20171122090325.29458-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.cz \
--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).