linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Arne Jansen <sensille@gmx.net>
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 3/6] btrfs: add scrub code and prototypes
Date: Wed, 16 Mar 2011 16:35:25 +0200	[thread overview]
Message-ID: <20110316143525.GA2546@kwango.lan.net> (raw)
In-Reply-To: <7ccafb5250b72ca706369a8d5b45f06e8d5a4f8a.1299941055.git.sensille@gmx.net>

On Sat, Mar 12, 2011 at 03:50:42PM +0100, Arne Jansen wrote:

All extent maps are leaked after unmount.  lookup_extent_mapping() takes
a reference, so they are all left with em->refs = 1.  I suggest the
following:

> +static noinline_for_stack int scrub_chunk(struct scrub_dev *sdev, 
> +	u64 chunk_tree, u64 chunk_objectid, u64 chunk_offset, u64 length)
> +{
> +	struct btrfs_mapping_tree *map_tree =
> +		&sdev->dev->dev_root->fs_info->mapping_tree;
> +	struct map_lookup *map;
> +	struct extent_map *em;
> +	int i;
> +	int ret;
> +
> +	read_lock(&map_tree->map_tree.lock);
> +	em = lookup_extent_mapping(&map_tree->map_tree, chunk_offset, 1);
> +	read_unlock(&map_tree->map_tree.lock);
> +
> +	if (!em)
> +		return -EINVAL;
> +
> +	map = (struct map_lookup *)em->bdev;
> +	if (em->start != chunk_offset)
> +		return -EINVAL;
> +
> +	if (em->len < length)
> +		return -EINVAL;
> +
> +	for (i = 0; i < map->num_stripes; ++i) {
> +		if (map->stripes[i].dev == sdev->dev) {
> +			ret = scrub_stripe(sdev, map, i, chunk_offset, length);
> +			if (ret)
> +				return ret;
> +		}
> +	}

+	free_extent_map(em);

> +	return 0;
> +}

Thanks,

		Ilya

  parent reply	other threads:[~2011-03-16 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 14:50 [PATCH v3 0/6] btrfs: scrub Arne Jansen
2011-03-12 14:50 ` [PATCH v3 1/6] btrfs: add parameter to btrfs_lookup_csum_range Arne Jansen
2011-03-12 14:50 ` [PATCH v3 2/6] btrfs: make struct map_lookup public Arne Jansen
2011-03-12 14:50 ` [PATCH v3 3/6] btrfs: add scrub code and prototypes Arne Jansen
2011-03-13 23:50   ` Ilya Dryomov
2011-03-14  9:57     ` Arne Jansen
2011-03-16 14:35   ` Ilya Dryomov [this message]
2011-03-16 14:54     ` Ilya Dryomov
2011-03-16 22:07   ` Andi Kleen
2011-03-16 23:10     ` Arne Jansen
2011-03-17 19:02       ` Arne Jansen
2011-03-12 14:50 ` [PATCH v3 4/6] btrfs: sync scrub with commit & device removal Arne Jansen
2011-03-12 14:50 ` [PATCH v3 5/6] btrfs: add state information for scrub Arne Jansen
2011-03-12 14:50 ` [PATCH v3 6/6] btrfs: new ioctls " Arne Jansen

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=20110316143525.GA2546@kwango.lan.net \
    --to=idryomov@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@gmx.net \
    /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).