From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix extent_from_logical to deal with skinny metadata
Date: Fri, 24 Jan 2014 09:07:39 +0800 [thread overview]
Message-ID: <52E1BCDB.9060004@cn.fujitsu.com> (raw)
In-Reply-To: <1390511177-3395-1-git-send-email-jbacik@fb.com>
Hello Josef,
I have sent a patch before to address this issue:
https://patchwork.kernel.org/patch/3472211/
I introduced another function btrfs_previous_extent_item() to
search previous extent item, I think you must miss my path before
giving this patch ^_^.
Thanks,
Wang
On 01/24/2014 05:06 AM, Josef Bacik wrote:
> I don't think this is an issue and I've not seen it in practice but
> extent_from_logical will fail to find a skinny extent because it uses
> btrfs_previous_item and gives it the normal extent item type. This is just not
> a place to use btrfs_previous_item since we care about either normal extents or
> skinny extents, so open code btrfs_previous_item to properly check. This would
> only affect metadata and the only place this is used for metadata is scrub and
> I'm pretty sure it's just for printing stuff out, not actually doing any work so
> hopefully it was never a problem other than a cosmetic one. Thanks,
>
> Signed-off-by: Josef Bacik <jbacik@fb.com>
> ---
> fs/btrfs/backref.c | 41 +++++++++++++++++++++++++++++++++--------
> 1 file changed, 33 insertions(+), 8 deletions(-)
>
> diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
> index 34a8952..dcf2448 100644
> --- a/fs/btrfs/backref.c
> +++ b/fs/btrfs/backref.c
> @@ -1302,20 +1302,45 @@ int extent_from_logical(struct btrfs_fs_info *fs_info, u64 logical,
> ret = btrfs_search_slot(NULL, fs_info->extent_root, &key, path, 0, 0);
> if (ret < 0)
> return ret;
> - ret = btrfs_previous_item(fs_info->extent_root, path,
> - 0, BTRFS_EXTENT_ITEM_KEY);
> - if (ret < 0)
> - return ret;
>
> - btrfs_item_key_to_cpu(path->nodes[0], found_key, path->slots[0]);
> + while (1) {
> + u32 nritems;
> + if (path->slots[0] == 0) {
> + btrfs_set_path_blocking(path);
> + ret = btrfs_prev_leaf(fs_info->extent_root, path);
> + if (ret != 0) {
> + if (ret > 0) {
> + pr_debug("logical %llu is not within "
> + "any extent\n", logical);
> + ret = -ENOENT;
> + }
> + return ret;
> + }
> + } else {
> + path->slots[0]--;
> + }
> + nritems = btrfs_header_nritems(path->nodes[0]);
> + if (nritems == 0) {
> + pr_debug("logical %llu is not within any extent\n",
> + logical);
> + return -ENOENT;
> + }
> + if (path->slots[0] == nritems)
> + path->slots[0]--;
> +
> + btrfs_item_key_to_cpu(path->nodes[0], found_key,
> + path->slots[0]);
> + if (found_key->type == BTRFS_EXTENT_ITEM_KEY ||
> + found_key->type == BTRFS_METADATA_ITEM_KEY)
> + break;
> + }
> +
> if (found_key->type == BTRFS_METADATA_ITEM_KEY)
> size = fs_info->extent_root->leafsize;
> else if (found_key->type == BTRFS_EXTENT_ITEM_KEY)
> size = found_key->offset;
>
> - if ((found_key->type != BTRFS_EXTENT_ITEM_KEY &&
> - found_key->type != BTRFS_METADATA_ITEM_KEY) ||
> - found_key->objectid > logical ||
> + if (found_key->objectid > logical ||
> found_key->objectid + size <= logical) {
> pr_debug("logical %llu is not within any extent\n", logical);
> return -ENOENT;
next prev parent reply other threads:[~2014-01-24 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 21:06 [PATCH] Btrfs: fix extent_from_logical to deal with skinny metadata Josef Bacik
2014-01-24 1:07 ` Wang Shilong [this message]
2014-01-24 14:51 ` Josef Bacik
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=52E1BCDB.9060004@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.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.