From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Filipe Manana <fdmanana@suse.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: correctly get tree level in tree_backref_for_extent
Date: Tue, 16 Dec 2014 10:44:06 +0900 [thread overview]
Message-ID: <548F8E66.2050809@jp.fujitsu.com> (raw)
In-Reply-To: <1418659482-11734-1-git-send-email-fdmanana@suse.com>
(2014/12/16 1:04), Filipe Manana wrote:
> If we are using skinny metadata, the block's tree level is in the offset
> of the key and not in a btrfs_tree_block_info structure following the
> extent item (it doesn't exist). Therefore fix it.
Yes, this key type is introduced by commit 3173a18.
fs/btrfs/ctree.h
======================
/*
* The same as the BTRFS_EXTENT_ITEM_KEY, except it's metadata we already know
* the length, so we save the level in key->offset instead of the length.
*/
#define BTRFS_METADATA_ITEM_KEY 169
======================
>
> Besides returning the correct level in the tree, this also prevents reading
> past the leaf's end in the case where the extent item is the last item in
> the leaf (eb) and it has only 1 inline reference - this is because
> sizeof(struct btrfs_tree_block_info) is greater than
> sizeof(struct btrfs_extent_inline_ref).
>
> Got it while running a scrub which produced the following warning:
>
> BTRFS: checksum error at logical 42123264 on dev /dev/sde, sector 15840: metadata node (level 24) in tree 5
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
In addition, build v3.18 + this patch succeeded without any warning.
Thanks,
Satoru
> ---
> fs/btrfs/backref.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
> index 2d3e32e..8729cf6 100644
> --- a/fs/btrfs/backref.c
> +++ b/fs/btrfs/backref.c
> @@ -1552,7 +1552,6 @@ int tree_backref_for_extent(unsigned long *ptr, struct extent_buffer *eb,
> {
> int ret;
> int type;
> - struct btrfs_tree_block_info *info;
> struct btrfs_extent_inline_ref *eiref;
>
> if (*ptr == (unsigned long)-1)
> @@ -1573,9 +1572,17 @@ int tree_backref_for_extent(unsigned long *ptr, struct extent_buffer *eb,
> }
>
> /* we can treat both ref types equally here */
> - info = (struct btrfs_tree_block_info *)(ei + 1);
> *out_root = btrfs_extent_inline_ref_offset(eb, eiref);
> - *out_level = btrfs_tree_block_level(eb, info);
> +
> + if (key->type == BTRFS_EXTENT_ITEM_KEY) {
> + struct btrfs_tree_block_info *info;
> +
> + info = (struct btrfs_tree_block_info *)(ei + 1);
> + *out_level = btrfs_tree_block_level(eb, info);
> + } else {
> + ASSERT(key->type == BTRFS_METADATA_ITEM_KEY);
> + *out_level = (u8)key->offset;
> + }
>
> if (ret == 1)
> *ptr = (unsigned long)-1;
>
prev parent reply other threads:[~2014-12-16 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 16:04 [PATCH] Btrfs: correctly get tree level in tree_backref_for_extent Filipe Manana
2014-12-16 1:44 ` Satoru Takeuchi [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=548F8E66.2050809@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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.