From: riteshh <riteshh@linux.ibm.com>
To: zhanchengbin <zhanchengbin1@huawei.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, liuzhiqiang26@huawei.com,
linfeilong@huawei.com
Subject: Re: [PATCH v2] setup_tdb : fix memory leak
Date: Tue, 4 Jan 2022 17:07:49 +0530 [thread overview]
Message-ID: <20220104113749.meyk7zkdtrqgwoc2@riteshh-domain> (raw)
In-Reply-To: <968b7f2c-6030-35c3-bc65-06a80b6e2403@huawei.com>
On 22/01/04 07:21PM, zhanchengbin wrote:
> In setup_tdb(), need free tdb_dir and db->tdb_fn before return,
> otherwise it will cause memory leak.
>
> Signed-off-by: zhanchengbin <zhanchengbin1@huawei.com>
> Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
> ---
> e2fsck/dirinfo.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/e2fsck/dirinfo.c b/e2fsck/dirinfo.c
> index 49d624c5..97a303e5 100644
> --- a/e2fsck/dirinfo.c
> +++ b/e2fsck/dirinfo.c
> @@ -49,7 +49,7 @@ static void setup_tdb(e2fsck_t ctx, ext2_ino_t num_dirs)
> ext2_ino_t threshold;
> errcode_t retval;
> mode_t save_umask;
> - char *tdb_dir, uuid[40];
> + char *tdb_dir = NULL, uuid[40];
> int fd, enable;
>
> profile_get_string(ctx->profile, "scratch_files", "directory", 0, 0,
> @@ -61,11 +61,11 @@ static void setup_tdb(e2fsck_t ctx, ext2_ino_t num_dirs)
>
> if (!enable || !tdb_dir || access(tdb_dir, W_OK) ||
> (threshold && num_dirs <= threshold))
> - return;
> + goto tdb_dir_error;
>
> retval = ext2fs_get_mem(strlen(tdb_dir) + 64, &db->tdb_fn);
> if (retval)
> - return;
> + goto tdb_dir_error;
>
> uuid_unparse(ctx->fs->super->s_uuid, uuid);
> sprintf(db->tdb_fn, "%s/%s-dirinfo-XXXXXX", tdb_dir, uuid);
> @@ -74,7 +74,7 @@ static void setup_tdb(e2fsck_t ctx, ext2_ino_t num_dirs)
> umask(save_umask);
> if (fd < 0) {
> db->tdb = NULL;
> - return;
> + goto tdb_fn_error;
> }
>
> if (num_dirs < 99991)
> @@ -83,6 +83,16 @@ static void setup_tdb(e2fsck_t ctx, ext2_ino_t num_dirs)
> db->tdb = tdb_open(db->tdb_fn, num_dirs, TDB_NOLOCK | TDB_NOSYNC,
> O_RDWR | O_CREAT | O_TRUNC, 0600);
> close(fd);
> +
> + return;
> +
> +tdb_fn_error:
> + ext2fs_free_mem(&db->tdb_fn);
> + db->tdb_fn = NULL;
I think making tdb_fn = NULL is not needed, since ext2fs_free_mem() takes care of it.
With that removed, feel free to add:
Reviewed-by: Ritesh Harjani <riteshh@linux.ibm.com>
-riteshh
> +tdb_dir_error:
> + if (tdb_dir) {
> + free(tdb_dir);
> + }
> }
> #endif
>
> --
> 2.27.0
>
prev parent reply other threads:[~2022-01-04 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 11:21 [PATCH v2] setup_tdb : fix memory leak zhanchengbin
2022-01-04 11:37 ` riteshh [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=20220104113749.meyk7zkdtrqgwoc2@riteshh-domain \
--to=riteshh@linux.ibm.com \
--cc=linfeilong@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=tytso@mit.edu \
--cc=zhanchengbin1@huawei.com \
/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