public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: "Geyslan G. Bem" <geyslan@gmail.com>
Cc: <chris.mason@fusionio.com>, <linux-btrfs@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kernel-br@googlegroups.com>
Subject: Re: [PATCH v3] btrfs: Fix memory leakage in the tree-log.c
Date: Wed, 9 Oct 2013 20:52:20 -0400	[thread overview]
Message-ID: <20131010005220.GI16461@localhost.localdomain> (raw)
In-Reply-To: <1381362030-29595-1-git-send-email-geyslan@gmail.com>

On Wed, Oct 09, 2013 at 08:40:30PM -0300, Geyslan G. Bem wrote:
> In some cases, add_inode_ref() is returning without freeing
> the 'name' pointer.
> 
> Added bail out to explicitly call kfree when necessary.
> 
> Signed-off-by: Geyslan G. Bem <geyslan@gmail.com>
> ---
>  fs/btrfs/tree-log.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
> index 79f057c..ad7cc5f 100644
> --- a/fs/btrfs/tree-log.c
> +++ b/fs/btrfs/tree-log.c
> @@ -1170,13 +1170,16 @@ static noinline int add_inode_ref(struct btrfs_trans_handle *trans,
>  			if (!dir)
>  				dir = read_one_inode(root, parent_objectid);
>  			if (!dir)
> -				return -ENOENT;
> +			{
> +				ret = -ENOENT;
> +				goto bail;
> +			}

Code formatting is

if () {
}

not

if ()
{
}


>  		} else {
>  			ret = ref_get_fields(eb, ref_ptr, &namelen, &name,
>  					     &ref_index);
>  		}
>  		if (ret)
> -			return ret;
> +			goto bail;
>  
>  		/* if we already have a perfect match, we're done */
>  		if (!inode_in_dir(root, path, btrfs_ino(dir), btrfs_ino(inode),
> @@ -1227,6 +1230,9 @@ out:
>  	btrfs_release_path(path);
>  	iput(dir);
>  	iput(inode);
> +bail:
> +	if (name)
> +		kfree(name);

kfree already does the if (name) part of this so this is redundant.  Also if you
are going to do this you need to set name = NULL; after the kfree above it
otherwise we have a double free.  Thanks,

Josef

  parent reply	other threads:[~2013-10-10  0:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 23:40 [PATCH v3] btrfs: Fix memory leakage in the tree-log.c Geyslan G. Bem
2013-10-09 23:46 ` Geyslan Gregório Bem
2013-10-10  0:52 ` Josef Bacik [this message]
2013-10-10  1:19   ` Geyslan Gregório Bem

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=20131010005220.GI16461@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=chris.mason@fusionio.com \
    --cc=geyslan@gmail.com \
    --cc=kernel-br@googlegroups.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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