From: Su Yue <Damenly_Su@gmx.com>
To: damenly.su@gmail.com, linux-btrfs@vger.kernel.org
Cc: suy.fnst@cn.fujitsu.com
Subject: Re: [PATCH 0/6] btrfs-progs: lowmem: bug fixes and inode_extref repair
Date: Wed, 12 Sep 2018 20:35:29 +0800 [thread overview]
Message-ID: <5ca64cd2-2117-f626-e56c-2e8e5e040c9e@gmx.com> (raw)
In-Reply-To: <20180912192046.5861-1-suy.fnst@cn.fujitsu.com>
Sorry for the noise, Please ignore this patchset.
Will send v2.
On 2018/9/13 3:20 AM, damenly.su@gmail.com wrote:
> From: Su Yue <suy.fnst@cn.fujitsu.com>
>
> This patchset can be fetched from my github(based on v4.17.1):
> https://github.com/Damenly/btrfs-progs/tree/lowmem_extref
>
> The patchset aims to support check and repair errors about
> inode_extref in lowmem mode.
>
> patch[1-2] let btrfs_unlink() detect inode_extref.
> patch[3] fixes a minor bug in check_dir_item due to my careless
> long ago.
> patch[4] fixes a bug about inconsistent path in check_fs_roots()
> under repair.
> patch[5] fixes a corner case about traversal of inode items.
> patch[6] enable inode_extref repair support and remove unnecessary
> checks.
> patch[7] add a test image, it can verify above patches except
> patch[3].
>
>
> Su Yue (6):
> btrfs-progs: adjust arguments of btrfs_lookup_inode_extref()
> btrfs-progs: make btrfs_unlink() lookup inode_extref
> btrfs-progs: lowmem check: find dir_item by di_key in check_dir_item()
> btrfs-progs: lowmem: search key of root again after check_fs_root()
> under repair
> btrfs-progs: lowmem: continue to check item in last slot while
> checking inodes
> btrfs-progs: lowmem: optimization and repair for check_inode_extref()
>
> check/mode-lowmem.c | 148 +++++++++++++++++++++++++++++++++++---------
> ctree.h | 6 +-
> inode-item.c | 6 +-
> inode.c | 14 ++++-
> 4 files changed, 139 insertions(+), 35 deletions(-)
>
next prev parent reply other threads:[~2018-09-12 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 19:20 [PATCH 0/6] btrfs-progs: lowmem: bug fixes and inode_extref repair damenly.su
2018-09-12 12:35 ` Su Yue [this message]
2018-09-12 19:20 ` [PATCH 1/6] btrfs-progs: adjust arguments of btrfs_lookup_inode_extref() damenly.su
2018-09-12 19:20 ` [PATCH 2/6] btrfs-progs: make btrfs_unlink() lookup inode_extref damenly.su
2018-09-12 19:20 ` [PATCH 3/6] btrfs-progs: lowmem check: find dir_item by di_key in check_dir_item() damenly.su
2018-09-12 19:20 ` [PATCH 4/6] btrfs-progs: lowmem: search key of root again after check_fs_root() under repair damenly.su
2018-09-12 19:20 ` [PATCH 5/6] btrfs-progs: lowmem: continue to check item in last slot while checking inodes damenly.su
2018-09-12 19:20 ` [PATCH 5/7] btrfs-progs: lowmem: improve check_inode_extref() damenly.su
2018-09-12 19:20 ` [PATCH 6/7] btrfs-progs: lowmem: continue to check item in last slot while checking inodes damenly.su
2018-09-12 19:20 ` [PATCH 6/6] btrfs-progs: lowmem: optimization and repair for check_inode_extref() damenly.su
2018-09-12 19:20 ` [PATCH 7/7] btrfs-progs: fsck-tests: add test case inode_extref without dir_item and dir_index damenly.su
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=5ca64cd2-2117-f626-e56c-2e8e5e040c9e@gmx.com \
--to=damenly_su@gmx.com \
--cc=damenly.su@gmail.com \
--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 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).