From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 05/15] btrfs-progs: lowmem check: let check_dir_item() continue if find wrong inode_item
Date: Fri, 26 Jan 2018 17:36:34 +0800 [thread overview]
Message-ID: <2db3f205-5969-98fd-32b8-1c8e68b89eb9@gmx.com> (raw)
In-Reply-To: <20180126083519.28373-6-suy.fnst@cn.fujitsu.com>
[-- Attachment #1.1: Type: text/plain, Size: 1281 bytes --]
On 2018年01月26日 16:35, Su Yue wrote:
> check_dir_item can handle missed/mismatched inode item well.
> Let it continue to check corresponding dir_item/index and inode_ref.
>
> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> cmds-check.c | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/cmds-check.c b/cmds-check.c
> index e33dd7db0048..eb65a18fe64b 100644
> --- a/cmds-check.c
> +++ b/cmds-check.c
> @@ -5984,15 +5984,12 @@ begin:
> ret = btrfs_search_slot(NULL, root, &location, path, 0, 0);
> if (ret) {
> tmp_err |= INODE_ITEM_MISSING;
> - goto next;
> - }
> -
> - ii = btrfs_item_ptr(path->nodes[0], path->slots[0],
> - struct btrfs_inode_item);
> - mode = btrfs_inode_mode(path->nodes[0], ii);
> - if (imode_to_type(mode) != filetype) {
> - tmp_err |= INODE_ITEM_MISMATCH;
> - goto next;
> + } else {
> + ii = btrfs_item_ptr(path->nodes[0], path->slots[0],
> + struct btrfs_inode_item);
> + mode = btrfs_inode_mode(path->nodes[0], ii);
> + if (imode_to_type(mode) != filetype)
> + tmp_err |= INODE_ITEM_MISMATCH;
> }
>
> /* Check relative INODE_REF/INODE_EXTREF */
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2018-01-26 9:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 8:35 [PATCH 00/15] btrfs-progs: fix filetype mismatch in check Su Yue
2018-01-26 8:35 ` [PATCH 01/15] btrfs-progs: lowmem check: introduce repair_inode_item_mismatch() Su Yue
2018-01-26 8:35 ` [PATCH 02/15] btrfs-progs: lowmem check: find and guess inode filetype Su Yue
2018-01-26 8:49 ` Qu Wenruo
2018-01-26 9:14 ` Qu Wenruo
2018-01-26 9:21 ` Qu Wenruo
2018-01-26 9:31 ` Su Yue
2018-01-26 9:35 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 03/15] btrfs-progs: lowmem check: find filetype in repair_inode_missing() Su Yue
2018-01-26 9:22 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 04/15] btrfs-progs: lowmem check: repair complex cases in repair_dir_item() Su Yue
2018-01-26 9:33 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 05/15] btrfs-progs: lowmem check: let check_dir_item() continue if find wrong inode_item Su Yue
2018-01-26 9:36 ` Qu Wenruo [this message]
2018-01-26 8:35 ` [PATCH 06/15] btrfs-progs: lowmem check: let check_dir_item() return if repaired Su Yue
2018-01-26 9:43 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 07/15] btrfs-progs: lowmem check: find_dir_item by di_key in check_dir_item() Su Yue
2018-01-26 9:37 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 08/15] btrfs-progs: lowmem check: call get_dir_isize() after repair Su Yue
2018-01-26 8:35 ` [PATCH 09/15] btrfs-progs: lowmem check: change logic of leaf process if repair Su Yue
2018-01-26 10:01 ` Qu Wenruo
2018-01-26 10:15 ` Su Yue
2018-01-26 8:35 ` [PATCH 10/15] btrfs-progs: check: clear I_ERR_FILE_EXTENT_DISCOUNT after repair Su Yue
2018-01-26 10:02 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 11/15] btrfs-progs: check: modify indoe_rec and backref " Su Yue
2018-01-26 8:35 ` [PATCH 12/15] btrfs-progs: check: increase counter error in check_inode_recs() Su Yue
2018-01-26 10:05 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 13/15] btrfs-progs: check: find inode filetype in create_inode_item() Su Yue
2018-01-26 10:11 ` Qu Wenruo
2018-01-26 8:35 ` [PATCH 14/15] btrfs-progs: check: handle mismatched filetype in repair_inode_backref Su Yue
2018-01-26 8:35 ` [PATCH 15/15] btrfs-progs: fsck-tests: add image for original and lowmem check Su Yue
2018-01-26 10:17 ` 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=2db3f205-5969-98fd-32b8-1c8e68b89eb9@gmx.com \
--to=quwenruo.btrfs@gmx.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).