linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Block <ablock84@googlemail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] Btrfs: merge inode_list in __merge_refs
Date: Thu, 8 Nov 2012 22:35:19 +0100	[thread overview]
Message-ID: <CAB9VWqAJZCr5HiHwpisiuKNq0Rarba9YL9SfxudssR9YcQ75sA@mail.gmail.com> (raw)
In-Reply-To: <1352410044-10547-1-git-send-email-ablock84@googlemail.com>

On Thu, Nov 8, 2012 at 10:27 PM, Alexander Block
<ablock84@googlemail.com> wrote:
> When __merge_refs merges two refs, it is also needed to merge the
> inode_list of both refs. Otherwise we have missed backrefs and memory
> leaks. This happens for example if two inodes share an extent and
> both lie in the same leaf and thus also have the same parent.
>
> Signed-off-by: Alexander Block <ablock84@googlemail.com>
> Reviewed-by: Jan Schmidt <list.btrfs@jan-o-sch.net>
> ---
>  fs/btrfs/backref.c |   13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
> index 208d8aa..aea6d2d 100644
> --- a/fs/btrfs/backref.c
> +++ b/fs/btrfs/backref.c
> @@ -461,6 +461,7 @@ static int __merge_refs(struct list_head *head, int mode)
>                      pos2 = n2, n2 = pos2->next) {
>                         struct __prelim_ref *ref2;
>                         struct __prelim_ref *xchg;
> +                       struct extent_inode_elem *eie;
>
>                         ref2 = list_entry(pos2, struct __prelim_ref, list);
>
> @@ -472,12 +473,20 @@ static int __merge_refs(struct list_head *head, int mode)
>                                         ref1 = ref2;
>                                         ref2 = xchg;
>                                 }
> -                               ref1->count += ref2->count;
>                         } else {
>                                 if (ref1->parent != ref2->parent)
>                                         continue;
> -                               ref1->count += ref2->count;
>                         }
> +
> +                       eie = ref1->inode_list;
> +                       while (eie && eie->next)
> +                               eie = eie->next;
> +                       if (eie)
> +                               eie->next = ref2->inode_list;
> +                       else
> +                               ref1->inode_list = ref2->inode_list;
> +                       ref1->count += ref2->count;
> +
>                         list_del(&ref2->list);
>                         kfree(ref2);
>                 }
> --
> 1.7.10.4
>

Used wrong CC for stable list. Corrected now.

  reply	other threads:[~2012-11-08 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 21:27 [PATCH] Btrfs: merge inode_list in __merge_refs Alexander Block
2012-11-08 21:35 ` Alexander Block [this message]
2012-11-09  7:01   ` Greg KH

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=CAB9VWqAJZCr5HiHwpisiuKNq0Rarba9YL9SfxudssR9YcQ75sA@mail.gmail.com \
    --to=ablock84@googlemail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).