linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Maxim Korotkov <korotkov.maxim.s@gmail.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Maxim Korotkov <maskorotkov@rasu.ru>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] fsck.f2fs: fix memleak in f2fs_create()
Date: Fri, 2 Jun 2023 17:44:17 +0800	[thread overview]
Message-ID: <06a2e4dc-fb28-24cf-0a41-3c281a9b2848@kernel.org> (raw)
In-Reply-To: <20230531072238.370186-1-korotkov.maxim.s@gmail.com>

On 2023/5/31 15:22, Maxim Korotkov wrote:
> In error handling cases, exiting a function without releasing memory
> Added tags to clean up resources and return error code
> Found by RASU JSC
> Signed-off-by: Maxim Korotkov <maskorotkov@rasu.ru>
> ---
>   fsck/dir.c | 9 +++++++--
>   1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/fsck/dir.c b/fsck/dir.c
> index 4a3eb6e..c3508bf 100644
> --- a/fsck/dir.c
> +++ b/fsck/dir.c
> @@ -704,7 +704,7 @@ int f2fs_create(struct f2fs_sb_info *sbi, struct dentry *de)
>   	ret = convert_inline_dentry(sbi, parent, ni.blk_addr);
>   	if (ret) {
>   		MSG(0, "Convert inline dentry for pino=%x failed.\n", de->pino);
> -		return -1;
> +		goto err_free_parent_dir;

How about:

	ret = -1
	goto free_parent_dir;

>   	}
>   
>   	ret = f2fs_find_entry(sbi, parent, de);
> @@ -728,7 +728,7 @@ int f2fs_create(struct f2fs_sb_info *sbi, struct dentry *de)
>   		if (hardlink_ni.blk_addr == NULL_ADDR) {
>   			MSG(1, "No original inode for hard link to_ino=%x\n",
>   				found_hardlink->to_ino);
> -			return -1;
> +			goto err_free_child_dir;
	ret = -1
	goto free_child_dir;

>   		}
>   
>   		/* Use previously-recorded inode */
> @@ -805,6 +805,11 @@ free_child_dir:
>   free_parent_dir:
>   	free(parent);
>   	return 0;

	return ret;

Thanks,

> +err_free_child_dir:
> +	free(child);
> +err_free_parent_dir:
> +	free(parent);
> +	return -1;	
>   }
>   
>   int f2fs_mkdir(struct f2fs_sb_info *sbi, struct dentry *de)


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2023-06-02  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  7:22 [f2fs-dev] [PATCH] fsck.f2fs: fix memleak in f2fs_create() Maxim Korotkov
2023-06-02  9:44 ` Chao Yu [this message]

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=06a2e4dc-fb28-24cf-0a41-3c281a9b2848@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=korotkov.maxim.s@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=maskorotkov@rasu.ru \
    /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).