linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: Check the consistence between the parent node and child node/leaf.
Date: Wed, 1 Oct 2014 11:49:24 -0400	[thread overview]
Message-ID: <1412178564.9583.1@mail.thefacebook.com> (raw)
In-Reply-To: <1411716995-22537-1-git-send-email-quwenruo@cn.fujitsu.com>

On Fri, Sep 26, 2014 at 3:36 AM, Qu Wenruo <quwenruo@cn.fujitsu.com> 
wrote:
> When btrfs-progs walk down the tree, it does not check whether the 
> child
> node/leaf is valid.
> In fact, there is some corrupted image whose csum is all valid but
> parent node points to a invalid leaf.
> 
> In my case, the parent node in fs tree point to a invalid leaf(gen 
> 11),
> whose generation(15) and first key(EXTENT_TREE ROOT_ITEM 0) is
> completely invalid, and will cause BUG_ON in process_inode_item().
> 
> Unfortunately, we are unable to fix when it happens.
> So we can only output meaningful error message and avoid the insane
> node/leaf, which is still much better than the original BUG_ON().
> 
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
>  cmds-check.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 51 insertions(+)
> 
> diff --git a/cmds-check.c b/cmds-check.c
> index d479361..9471709 100644
> --- a/cmds-check.c
> +++ b/cmds-check.c
> @@ -1302,6 +1302,52 @@ static void reada_walk_down(struct btrfs_root 
> *root,
>  	}
>  }
> 
> +/*
> + * Check the child node/leaf by the following condition:
> + * 1. the first item key of the node/leaf should be the same with 
> the one
> + *    in parent.
> + * 2. block in parent node should match the child node/leaf.
> + * 3. generation of parent node and child's header should be 
> consistent.
> + *
> + * Or the child node/leaf pointed by the key in parent is not valid.
> + *
> + * We hope to check leaf owner too, but since subvol may share 
> leaves,
> + * which makes leaf owner check not so strong, key check should be
> + * sufficient enough for that case.
> + */
> +static int check_child_node(struct btrfs_root *root,
> +			    struct extent_buffer *parent, int slot,
> +			    struct extent_buffer *child)
> +{
> +	struct btrfs_key parent_key;
> +	struct btrfs_key child_key;
> +	int ret = 0;
> +
> +	btrfs_item_key_to_cpu(parent, &parent_key, slot);

Dave mentioned he was getting a bunch of Wrong key of child node 
messages from his current tree.  I should have spotted it sooner, but 
this call should be btrfs_node_key_to_cpu(), since the parent is always 
a node.

> 
> +	btrfs_item_key_to_cpu(child, &child_key, 0);

This should check the level and only use btrfs_item_key_to_cpu on the 
leaves.

Thanks!

-chris



  reply	other threads:[~2014-10-01 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  7:36 [PATCH] btrfs-progs: Check the consistence between the parent node and child node/leaf Qu Wenruo
2014-10-01 15:49 ` Chris Mason [this message]
2014-10-06  1:20   ` 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=1412178564.9583.1@mail.thefacebook.com \
    --to=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@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).