From: Josef Bacik <josef@toxicpanda.com>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC ONLY 6/8] btrfs: add code to read raid extent
Date: Mon, 16 May 2022 10:55:18 -0400 [thread overview]
Message-ID: <YoJl1jo5hgDLxFi+@localhost.localdomain> (raw)
In-Reply-To: <2aa8aae2f6394b774f480d877f2701fed6fd74c4.1652711187.git.johannes.thumshirn@wdc.com>
On Mon, May 16, 2022 at 07:31:41AM -0700, Johannes Thumshirn wrote:
> Add boilerplate code to lookup the physical address from the
> raid-stripe-tree when a read on an RAID volume formatted with the
> raid-stripe-tree was attempted.
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> ---
> fs/btrfs/raid-stripe-tree.c | 68 +++++++++++++++++++++++++++++++++++++
> fs/btrfs/raid-stripe-tree.h | 3 ++
> fs/btrfs/volumes.c | 23 +++++++++++--
> 3 files changed, 91 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/raid-stripe-tree.c b/fs/btrfs/raid-stripe-tree.c
> index 370ea68fe343..ecc8205be760 100644
> --- a/fs/btrfs/raid-stripe-tree.c
> +++ b/fs/btrfs/raid-stripe-tree.c
> @@ -1,10 +1,78 @@
> // SPDX-License-Identifier: GPL-2.0
>
> +#include <linux/btrfs_tree.h>
> +
> #include "ctree.h"
> #include "transaction.h"
> #include "disk-io.h"
> #include "raid-stripe-tree.h"
> #include "volumes.h"
> +#include "misc.h"
> +
> +int btrfs_get_raid_extent_offset(struct btrfs_fs_info *fs_info,
> + u64 logical, u64 length, u64 map_type,
> + u64 devid, u64 *physical)
> +{
> + struct btrfs_root *stripe_root = fs_info->stripe_root;
> + struct btrfs_dp_stripe *raid_stripe;
> + struct btrfs_key stripe_key;
> + struct btrfs_key found_key;
> + struct btrfs_path *path;
> + struct extent_buffer *leaf;
> + u64 offset;
> + u64 found_logical, found_length;
> + int num_stripes;
> + int slot;
> + int ret;
> + int i;
> +
> + stripe_key.objectid = logical;
> + stripe_key.type = BTRFS_RAID_STRIPE_KEY;
> + stripe_key.offset = length;
> +
> + path = btrfs_alloc_path();
> + if (!path)
> + return -ENOMEM;
> +
> + num_stripes = btrfs_bg_type_to_factor(map_type);
> +
> + ret = btrfs_search_slot_for_read(stripe_root, &stripe_key, path, 0, 0);
> + if (ret < 0) {
> + goto out;
> + }
> +
> + if (ret == 1)
> + ret = 0;
> +
> + while (1) {
> + leaf = path->nodes[0];
> + slot = path->slots[0];
> +
> + btrfs_item_key_to_cpu(leaf, &found_key, slot);
> + found_logical = found_key.objectid;
> + found_length = found_key.offset;
> +
> + if (!in_range(logical, found_logical, found_length))
> + goto next;
> + offset = logical - found_logical;
> +
> + raid_stripe = btrfs_item_ptr(leaf, slot, struct btrfs_dp_stripe);
> + for (i = 0; i < num_stripes; i++) {
> + if (btrfs_stripe_extent_devid_nr(leaf, raid_stripe, i) != devid)
> + continue;
> + *physical = btrfs_stripe_extent_offset_nr(leaf, raid_stripe, i) + offset;
> + goto out;
> + }
> +next:
> + ret = btrfs_next_item(stripe_root, path);
> + if (ret)
This will leak 1 if we don't find a stripe, probably should do EUCLEAN if we
don't have a raid stripe for this? Thanks,
Josef
next prev parent reply other threads:[~2022-05-16 14:55 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 14:31 [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 1/8] btrfs: add raid stripe tree definitions Johannes Thumshirn
2022-05-17 7:39 ` Qu Wenruo
2022-05-17 7:45 ` Johannes Thumshirn
2022-05-17 7:56 ` Qu Wenruo
2022-05-16 14:31 ` [RFC ONLY 2/8] btrfs: move btrfs_io_context to volumes.h Johannes Thumshirn
2022-05-17 7:42 ` Qu Wenruo
2022-05-17 7:51 ` Johannes Thumshirn
2022-05-17 7:58 ` Qu Wenruo
2022-05-17 8:01 ` Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 3/8] btrfs: read raid-stripe-tree from disk Johannes Thumshirn
2022-05-17 8:09 ` Qu Wenruo
2022-05-17 8:13 ` Johannes Thumshirn
2022-05-17 8:28 ` Qu Wenruo
2022-05-18 11:29 ` Johannes Thumshirn
2022-05-19 8:36 ` Qu Wenruo
2022-05-19 8:39 ` Johannes Thumshirn
2022-05-19 10:37 ` Qu Wenruo
2022-05-19 11:44 ` Johannes Thumshirn
2022-05-19 11:48 ` Qu Wenruo
2022-05-19 11:53 ` Johannes Thumshirn
2022-05-19 13:26 ` Qu Wenruo
2022-05-19 13:49 ` Johannes Thumshirn
2022-05-19 22:56 ` Qu Wenruo
2022-05-20 8:27 ` Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 4/8] btrfs: add boilerplate code to insert raid extent Johannes Thumshirn
2022-05-17 7:53 ` Qu Wenruo
2022-05-17 8:00 ` Qu Wenruo
2022-05-17 8:05 ` Johannes Thumshirn
2022-05-17 8:09 ` Qu Wenruo
2022-05-16 14:31 ` [RFC ONLY 5/8] btrfs: add code to delete " Johannes Thumshirn
2022-05-17 8:06 ` Qu Wenruo
2022-05-17 8:10 ` Johannes Thumshirn
2022-05-17 8:14 ` Qu Wenruo
2022-05-17 8:20 ` Johannes Thumshirn
2022-05-17 8:31 ` Qu Wenruo
2022-05-16 14:31 ` [RFC ONLY 6/8] btrfs: add code to read " Johannes Thumshirn
2022-05-16 14:55 ` Josef Bacik [this message]
2022-05-16 14:31 ` [RFC ONLY 7/8] btrfs: zoned: allow zoned RAID1 Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 8/8] btrfs: add raid stripe tree pretty printer Johannes Thumshirn
2022-05-16 14:58 ` [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree Josef Bacik
2022-05-16 15:04 ` Johannes Thumshirn
2022-05-16 15:10 ` Josef Bacik
2022-05-16 15:47 ` Johannes Thumshirn
2022-05-17 7:23 ` Nikolay Borisov
2022-05-17 7:31 ` Qu Wenruo
2022-05-17 7:41 ` Johannes Thumshirn
2022-05-17 7:32 ` Johannes Thumshirn
2022-07-13 10:54 ` RAID56 discussion related to RST. (Was "Re: [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree") Qu Wenruo
2022-07-13 11:43 ` Johannes Thumshirn
2022-07-13 12:01 ` Qu Wenruo
2022-07-13 12:42 ` Johannes Thumshirn
2022-07-13 13:47 ` Qu Wenruo
2022-07-13 14:01 ` Johannes Thumshirn
2022-07-13 15:24 ` Lukas Straub
2022-07-13 15:28 ` Johannes Thumshirn
2022-07-14 1:08 ` Qu Wenruo
2022-07-14 7:08 ` Johannes Thumshirn
2022-07-14 7:32 ` Qu Wenruo
2022-07-14 7:46 ` Johannes Thumshirn
2022-07-14 7:53 ` Qu Wenruo
2022-07-15 17:54 ` Goffredo Baroncelli
2022-07-15 19:08 ` Thiago Ramon
2022-07-16 0:34 ` Qu Wenruo
2022-07-16 11:11 ` Qu Wenruo
2022-07-16 13:52 ` Thiago Ramon
2022-07-16 14:26 ` Goffredo Baroncelli
2022-07-17 17:58 ` Goffredo Baroncelli
2022-07-17 0:30 ` Qu Wenruo
2022-07-17 15:18 ` Thiago Ramon
2022-07-17 22:01 ` Qu Wenruo
2022-07-17 23:00 ` Zygo Blaxell
2022-07-18 1:04 ` Qu Wenruo
2022-07-15 20:14 ` Chris Murphy
2022-07-18 7:33 ` Johannes Thumshirn
2022-07-18 8:03 ` Qu Wenruo
2022-07-18 21:49 ` Forza
2022-07-19 1:19 ` Qu Wenruo
2022-07-21 14:51 ` Forza
2022-07-24 11:27 ` Qu Wenruo
2022-07-25 0:00 ` Zygo Blaxell
2022-07-25 0:25 ` Qu Wenruo
2022-07-25 5:41 ` Zygo Blaxell
2022-07-25 7:49 ` Qu Wenruo
2022-07-25 19:58 ` Goffredo Baroncelli
2022-07-25 21:29 ` Qu Wenruo
2022-07-18 7:30 ` Johannes Thumshirn
2022-07-19 18:58 ` Goffredo Baroncelli
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=YoJl1jo5hgDLxFi+@localhost.localdomain \
--to=josef@toxicpanda.com \
--cc=johannes.thumshirn@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox