All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Guanghao <wuguanghao3@huawei.com>
To: <linux-ext4@vger.kernel.org>
Cc: <liuzhiqiang26@huawei.com>, <linfeilong@huawei.com>
Subject: [PATCH 01/12] profile_create_node: set magic before strdup(name) to avoid memory leak
Date: Mon, 24 May 2021 19:19:48 +0800	[thread overview]
Message-ID: <fdcf04e8-7fad-886d-eaa2-c8a814269c03@huawei.com> (raw)
In-Reply-To: <266bc52e-e279-ce84-0e1f-1405b9bc6174@huawei.com>

If new->magic != PROF_MAGIC_NODE, profile_free_node() don't free node.
This will cause the node to be unable to be released correctly and
a memory leak will occur.

Signed-off-by: Wu Guanghao <wuguanghao3@huawei.com>
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Reviewed-by: Wu Bo <wubo40@huawei.com>
---
 lib/support/profile.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lib/support/profile.c b/lib/support/profile.c
index 585ed595..2eb3a9d1 100644
--- a/lib/support/profile.c
+++ b/lib/support/profile.c
@@ -1093,6 +1093,8 @@ errcode_t profile_create_node(const char *name, const char *value,
 	if (!new)
 		return ENOMEM;
 	memset(new, 0, sizeof(struct profile_node));
+	new->magic = PROF_MAGIC_NODE;
+
 	new->name = strdup(name);
 	if (new->name == 0) {
 	    profile_free_node(new);
@@ -1105,7 +1107,6 @@ errcode_t profile_create_node(const char *name, const char *value,
 		    return ENOMEM;
 		}
 	}
-	new->magic = PROF_MAGIC_NODE;

 	*ret_node = new;
 	return 0;
-- 

  reply	other threads:[~2021-05-24 11:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 11:18 [PATCH 00/12] e2fsprogs: some bugfixs and some code cleanups Wu Guanghao
2021-05-24 11:19 ` Wu Guanghao [this message]
2021-05-24 11:20 ` [PATCH 02/12] tdb_transaction_recover: fix memory leak Wu Guanghao
2021-05-24 11:20 ` [PATCH 03/12] zap_sector: " Wu Guanghao
2021-05-24 14:40   ` Благодаренко Артём
2021-05-25  2:16     ` Wu Guanghao
2021-05-24 11:21 ` [PATCH 04/12] ss_add_info_dir: fix memory leak and check whether,NULL pointer Wu Guanghao
2021-05-24 11:21 ` [PATCH 05/12] ss_create_invocation: fix memory leak and check whether NULL pointer Wu Guanghao
2021-05-24 11:23 ` [PATCH 06/12] append_pathname: check the value returned by realloc to avoid segfault Wu Guanghao
2021-05-25  9:37   ` Благодаренко Артём
2021-05-25 11:26     ` Wu Guanghao
2021-05-24 11:23 ` [PATCH 07/12] argv_parse: check return value of malloc in argv_parse() Wu Guanghao
2021-05-25  2:32   ` Wu Guanghao
2021-05-24 11:24 ` [PATCH 08/12] misc: fix potential segmentation fault problem in, scandir() Wu Guanghao
2021-05-24 11:24 ` [PATCH 09/12] lib/ss/error.c: check return value malloc in ss_name() Wu Guanghao
2021-05-24 11:25 ` [PATCH 10/12] hashmap: change return value type of, ext2fs_hashmap_add() Wu Guanghao
2021-05-25 12:45   ` Благодаренко Артём
2021-05-29  9:55     ` Zhiqiang Liu
2021-05-24 11:25 ` [PATCH 11/12] misc/lsattr: check whether path is NULL in, lsattr_dir_proc() Wu Guanghao
2021-05-24 11:26 ` [PATCH 12/12] ext2ed: fix potential NULL pointer dereference in, dupstr() Wu Guanghao

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=fdcf04e8-7fad-886d-eaa2-c8a814269c03@huawei.com \
    --to=wuguanghao3@huawei.com \
    --cc=linfeilong@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=liuzhiqiang26@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.