From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 04/15] btrfs-progs: lowmem check: repair complex cases in repair_dir_item()
Date: Fri, 26 Jan 2018 17:33:53 +0800 [thread overview]
Message-ID: <aae3aa94-d331-aada-9956-57f88ca8649e@gmx.com> (raw)
In-Reply-To: <20180126083519.28373-5-suy.fnst@cn.fujitsu.com>
[-- Attachment #1.1: Type: text/plain, Size: 5128 bytes --]
On 2018年01月26日 16:35, Su Yue wrote:
> If inode item is missing or filetype is corrupted maybe, and filetypes
> of dir_item and dir_index are corrupted too, lowmem repair may insert
> wrong inode item and dir_item/index.
>
> First, find and guess filetype of inode item, if failed, use
> BTRFS_REG_FILE as fallback for insertion.
> If filetype is not available, just delete current dir_item/index.
>
> And repair_dir_item also calls repair_inode_item_mismatch() now.
>
> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
Looks good.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> cmds-check.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 78 insertions(+), 17 deletions(-)
>
> diff --git a/cmds-check.c b/cmds-check.c
> index 08a2662e603c..e33dd7db0048 100644
> --- a/cmds-check.c
> +++ b/cmds-check.c
> @@ -2811,7 +2811,7 @@ static int walk_down_tree_v2(struct btrfs_trans_handle *trans,
>
> ret = check_child_node(cur, path->slots[*level], next);
> err |= ret;
> - if (ret < 0)
> + if (ret < 0)
> break;
>
> if (btrfs_is_leaf(next))
> @@ -5697,29 +5697,91 @@ static void print_dir_item_err(struct btrfs_root *root, struct btrfs_key *key,
> /*
> * Call repair_inode_item_missing and repair_ternary_lowmem to repair
> *
> + * @filetype: filetype of the dir_item/index
> + *
> * Returns error after repair
> */
> -static int repair_dir_item(struct btrfs_root *root, u64 dirid, u64 ino,
> - u64 index, u8 filetype, char *namebuf, u32 name_len,
> - int err)
> +static int repair_dir_item(struct btrfs_root *root, struct btrfs_key *key,
> + u64 ino, u64 index, u8 filetype, char *namebuf,
> + u32 name_len, int err)
> {
> int ret;
> + u64 dirid = key->objectid;
> + u8 true_filetype;
>
> - if (err & INODE_ITEM_MISSING) {
> - ret = repair_inode_item_missing(root, ino, filetype);
> - if (!ret)
> - err &= ~(INODE_ITEM_MISMATCH | INODE_ITEM_MISSING);
> + if (err & (INODE_ITEM_MISMATCH | INODE_ITEM_MISSING)) {
> + ret = find_file_type_lowmem(root, ino, &true_filetype);
> + if (ret) {
> + ret = guess_file_type_lowmem(root, ino,
> + &true_filetype);
> + if (ret) {
> + true_filetype = BTRFS_FT_REG_FILE;
> + error(
> + "can't get file type for inode %llu, using FILE as fallback",
> + ino);
> + }
> + }
> }
>
> - if (err & ~(INODE_ITEM_MISMATCH | INODE_ITEM_MISSING)) {
> - ret = repair_ternary_lowmem(root, dirid, ino, index, namebuf,
> - name_len, filetype, err);
> + /*
> + * Case: the dir_item has corresponding inode_ref but
> + * mismatch/missed inode_item and mismatch/missed another
> + * dir_item/index.
> + * repair_ternary_lowmem prefer to change another dir_item/index with
> + * wrong filetype. So delete the item here.
> + */
> + if (filetype != true_filetype &&
> + (err & (DIR_ITEM_MISMATCH | DIR_ITEM_MISSING) ||
> + err & (DIR_INDEX_MISMATCH | DIR_INDEX_MISSING))) {
> + struct btrfs_trans_handle *trans;
> + struct btrfs_path *path;
> +
> + path = btrfs_alloc_path();
> + if (!path)
> + goto out;
> + trans = btrfs_start_transaction(root, 0);
> + ret = btrfs_search_slot(trans, root, key, path, -1, 1);
> + if (ret) {
> + btrfs_commit_transaction(trans, root);
> + btrfs_release_path(path);
> + goto out;
> + }
> + ret = btrfs_del_item(trans, root, path);
> if (!ret) {
> - err &= ~(DIR_INDEX_MISMATCH | DIR_INDEX_MISSING);
> - err &= ~(DIR_ITEM_MISMATCH | DIR_ITEM_MISSING);
> - err &= ~(INODE_REF_MISSING);
> + err = 0;
> + printf(
> + "Deleted dir_item[%llu %u %llu]root %llu name %s filetype %u\n",
> + key->objectid, key->type, key->offset,
> + root->objectid, namebuf, filetype);
> }
> + btrfs_commit_transaction(trans, root);
> + btrfs_release_path(path);
> + /*
> + * Leave remains to check_inode_item() and check_inode_ref().
> + */
> + goto out;
> + }
> +
> + ret = repair_ternary_lowmem(root, dirid, ino, index, namebuf,
> + name_len, true_filetype, err);
> + if (!ret) {
> + err &= ~(DIR_INDEX_MISMATCH | DIR_INDEX_MISSING);
> + err &= ~(DIR_ITEM_MISMATCH | DIR_ITEM_MISSING);
> + err &= ~(INODE_REF_MISSING);
> + }
> +
> + if (err & INODE_ITEM_MISSING) {
> + ret = repair_inode_item_missing(root, ino, true_filetype);
> + if (!ret || ret == -EEXIST)
> + err &= ~INODE_ITEM_MISSING;
> }
> +
> + if (err & INODE_ITEM_MISMATCH) {
> + ret = repair_inode_item_mismatch(root, ino, true_filetype);
> + if (!ret)
> + err &= ~INODE_ITEM_MISMATCH;
> + }
> +out:
> return err;
> }
>
> @@ -5958,9 +6020,8 @@ begin:
> next:
>
> if (tmp_err && repair) {
> - ret = repair_dir_item(root, di_key->objectid,
> - location.objectid, index,
> - imode_to_type(mode), namebuf,
> + ret = repair_dir_item(root, di_key, location.objectid,
> + index, filetype, namebuf,
> name_len, tmp_err);
> if (ret != tmp_err) {
> need_research = 1;
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2018-01-26 9:34 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 [this message]
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
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=aae3aa94-d331-aada-9956-57f88ca8649e@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).