From: David Sterba <dsterba@suse.cz>
To: Su Yue <suy.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] btrfs-progs: check: original and lowmem mode fix
Date: Fri, 6 Oct 2017 18:52:40 +0200 [thread overview]
Message-ID: <20171006165239.GV3521@twin.jikos.cz> (raw)
In-Reply-To: <20170927063440.25961-1-suy.fnst@cn.fujitsu.com>
On Wed, Sep 27, 2017 at 02:34:35PM +0800, Su Yue wrote:
> The head three patches is independent from later two.
> Include:
> 1) Let check_extent_refs() return error instead of 0 if something wrong
> is found in original mode.
> 2) repair_root_items() should be called before any repair. Put it
> before do_check_chunks_and_extents();
> 3) Error status should not be modified if repair_root_items() succeeded
> in original repair.
>
> The late two patches are about invalid type in extent_inline_ref.
>
> Only original mode applied 001-003 patches can handle the case in the
> last patch. So I gather those 5 patches together.
>
>
> Su Yue (5):
> btrfs-progs: check: return value of check_extent_refs()
> btrfs-progs: check: call repair_root_items() before any repair
> btrfs-progs: check: error or return value of repair_root_items()
> btrfs-progs: check: check extent_inline_ref in lowmem
> btrfs-progs: fsck-tests: 027/bad_extent_inline_ref_type
1-5 applied, with minor adjustments. Thanks.
prev parent reply other threads:[~2017-10-06 16:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 6:34 [PATCH 0/5] btrfs-progs: check: original and lowmem mode fix Su Yue
2017-09-27 6:34 ` [PATCH 1/5] btrfs-progs: check: return value of check_extent_refs() Su Yue
2017-10-05 17:46 ` David Sterba
2017-10-06 1:38 ` Su Yue
2017-10-06 16:19 ` David Sterba
2017-10-06 1:42 ` Su Yue
2017-09-27 6:34 ` [PATCH 2/5] btrfs-progs: check: call repair_root_items() before any repair Su Yue
2017-09-27 7:24 ` Qu Wenruo
2017-09-27 7:58 ` [PATCH v2 " Su Yue
2017-09-27 8:28 ` [PATCH v3 " Su Yue
2017-09-27 6:34 ` [PATCH 3/5] btrfs-progs: check: error or return value of repair_root_items() Su Yue
2017-09-27 6:34 ` [PATCH 4/5] btrfs-progs: check: check extent_inline_ref in lowmem Su Yue
2017-09-27 6:34 ` [PATCH 5/5] btrfs-progs: fsck-tests: 027/bad_extent_inline_ref_type Su Yue
2017-10-06 16:52 ` David Sterba [this message]
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=20171006165239.GV3521@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=suy.fnst@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.