linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, chris@colorremedies.com
Subject: [PATCH 0/4] Lowmem mode btrfs fixes exposed by complex tree
Date: Mon, 13 Nov 2017 15:34:49 +0800	[thread overview]
Message-ID: <20171113073453.29198-1-wqu@suse.com> (raw)

The patchset (along with "backref lost" bug fixes and test cases) can be
fetched from github:
https://github.com/adam900710/btrfs-progs/tree/lowmem_fix

Despite the backref lost false alerts reported by Chris Murphy, there
are still some other bugs to be fixed.

One is also exposed by Chris Murphy, where btrfs-progs backref can't
handle shared block ref for metadata. Fix by 1st patch.

And 2 more bugs exposed by the test image which is originally designed
for the bug fixed by 1st patch.

Last but not the least, here comes the test image.
Which is an image with a lot of metadata and under a relocation.
It is definitely a bomb for old lowmem check.

Qu Wenruo (4):
  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

 backref.c                                          |   3 ++
 cmds-check.c                                       |  35 +++++++++++++++++----
 .../020-extent-ref-cases/shared_block_ref_only.img | Bin 0 -> 304128 bytes
 3 files changed, 32 insertions(+), 6 deletions(-)
 create mode 100644 tests/fsck-tests/020-extent-ref-cases/shared_block_ref_only.img

-- 
2.15.0


             reply	other threads:[~2017-11-13  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13  7:34 Qu Wenruo [this message]
2017-11-13  7:34 ` [PATCH 1/4] btrfs-progs: backref: Allow backref walk to handle direct parent ref Qu Wenruo
2017-11-13  7:34 ` [PATCH 2/4] btrfs-progs: lowmem check: Fix function call stack overflow caused by wrong tree reloc tree detection Qu Wenruo
2017-11-13  7:34 ` [PATCH 3/4] btrfs-progs: lowmem check: Fix false alerts for image with shared block ref only backref Qu Wenruo
2017-11-13  9:04 ` [PATCH 0/4] Lowmem mode btrfs fixes exposed by complex tree Qu Wenruo
2017-11-14  7:57 ` 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=20171113073453.29198-1-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=chris@colorremedies.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).