On Thu, Aug 08, 2013 at 01:04:17PM +0800, Wang Shilong wrote:
> Signed-off-by: Wang Shilong <wangsl.fnst@xxxxxxxxxxxxxx>
> Reviewed-by: Miao Xie <miaox@xxxxxxxxxxxxxx>
Sorry, I don't think I understand why it's a memory leak, some explanation
is needed here.
-liubo
> ---
> fs/btrfs/backref.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
> index cb73a12..54e7610 100644
> --- a/fs/btrfs/backref.c
> +++ b/fs/btrfs/backref.c
> @@ -911,7 +911,6 @@ again:
>
> while (!list_empty(&prefs)) {
> ref = list_first_entry(&prefs, struct __prelim_ref, list);
> - list_del(&ref->list);
> WARN_ON(ref->count < 0);
> if (ref->count && ref->root_id && ref->parent == 0) {
> /* no parent == root of tree */
> @@ -954,6 +953,7 @@ again:
> eie->next = ref->inode_list;
> }
> }
> + list_del(&ref->list);
> kfree(ref);
> }
>
> --
> 1.8.0.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html