From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Gaurav Singh <gaurav1086@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] librte_metrics: fix memory leak
Date: Sat, 1 Aug 2020 23:34:10 +0000 [thread overview]
Message-ID: <DB6PR0802MB2216C63BF55ABBEC0651972F984F0@DB6PR0802MB2216.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200801060838.20591-1-gaurav1086@gmail.com>
Hi Gaurav,
Thanks for the fix. Few comments inline. Also, please follow contributing guidelines [1]. There is a cheat sheet [2] which is very helpful.
[1] https://doc.dpdk.org/guides/contributing/index.html
[2] https://doc.dpdk.org/guides/contributing/cheatsheet.html
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Gaurav Singh
> Sent: Saturday, August 1, 2020 1:09 AM
> To: dev@dpdk.org
> Cc: Gaurav Singh <gaurav1086@gmail.com>
> Subject: [dpdk-dev] [PATCH] librte_metrics: fix memory leak
^^^^^^^^^^^^ should be 'lib/metrics'
>
>
> Fix memory leak issue
>
Needs "Fixes" tag and Cc to stable@dpdk.org (check the contribution guidelines)
> Signed-off-by: Gaurav Singh <gaurav1086@gmail.com>
> ---
> lib/librte_metrics/rte_metrics_telemetry.c | 24 +++++++++++++++-------
> 1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/lib/librte_metrics/rte_metrics_telemetry.c
> b/lib/librte_metrics/rte_metrics_telemetry.c
> index 289ebae0b..9fbe59c62 100644
> --- a/lib/librte_metrics/rte_metrics_telemetry.c
> +++ b/lib/librte_metrics/rte_metrics_telemetry.c
> @@ -41,12 +41,19 @@ rte_metrics_tel_reg_port_ethdev_to_metrics(uint16_t
> port_id)
> }
>
> xstats_names = malloc(sizeof(*xstats_names) * num_xstats);
> + if (xstats_names == NULL) {
> + METRICS_LOG_ERR("Failed to malloc memory for
> xstats_names");
> + ret = -ENOMEM;
> + return ret;
You can return -ENOMEM directly without assigning it to 'ret'
> + }
> +
> eth_xstats_names = malloc(sizeof(struct rte_eth_xstat_name)
> * num_xstats);
> - if (eth_xstats_names == NULL || xstats_names == NULL) {
> + if (eth_xstats_names == NULL) {
> METRICS_LOG_ERR("Failed to malloc memory for
> xstats_names");
^^^^^^^^^^^^ I think it is worth changing to eth_xstats_names
> ret = -ENOMEM;
> - goto free_xstats;
> + free(xstats_names);
> + return ret;
Same here, return -ENOMEM directly
> }
>
> if (rte_eth_xstats_get_names(port_id,
> @@ -54,7 +61,7 @@ rte_metrics_tel_reg_port_ethdev_to_metrics(uint16_t
> port_id)
> METRICS_LOG_ERR("rte_eth_xstats_get_names(%u) len %d
> failed",
> port_id, num_xstats);
> ret = -EPERM;
> - goto free_xstats;
> + return ret;
Any reason for this change? This change leaks memory.
> }
>
> for (i = 0; i < num_xstats; i++)
> @@ -63,9 +70,6 @@ rte_metrics_tel_reg_port_ethdev_to_metrics(uint16_t
> port_id)
> if (ret < 0)
> METRICS_LOG_ERR("rte_metrics_reg_names failed - metrics
> may already be registered");
>
> -free_xstats:
> - free(eth_xstats_names);
> - free(xstats_names);
Any reason for this change? This is leaking memory in the successful case.
> return ret;
> }
>
> @@ -167,9 +171,15 @@ rte_metrics_tel_format_port(uint32_t pid, json_t
> *ports,
> }
>
> metrics = malloc(sizeof(struct rte_metric_value) * num_metrics);
> + if (metrics == NULL) {
> + METRICS_LOG_ERR("Cannot allocate memory");
> + return -ENOMEM;
> + }
> +
> names = malloc(sizeof(struct rte_metric_name) * num_metrics);
> - if (metrics == NULL || names == NULL) {
> + if (names == NULL) {
> METRICS_LOG_ERR("Cannot allocate memory");
> + free(metrics);
> return -ENOMEM;
> }
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-08-01 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 3:45 [dpdk-dev] [PATCH] librte_metrics: fix memory leak Gaurav Singh
2020-07-31 4:54 ` Honnappa Nagarahalli
2020-08-01 1:46 ` Gaurav Singh
2020-08-01 6:08 ` Gaurav Singh
2020-08-01 23:34 ` Honnappa Nagarahalli [this message]
2020-08-08 16:39 ` [dpdk-dev] [PATCH] lib/metrics: " Gaurav Singh
2020-08-11 21:01 ` Honnappa Nagarahalli
2020-09-22 10:26 ` Power, Ciara
2020-10-30 14:59 ` David Marchand
2020-11-03 21:36 ` David Marchand
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=DB6PR0802MB2216C63BF55ABBEC0651972F984F0@DB6PR0802MB2216.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=gaurav1086@gmail.com \
--cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).