From: Jonathan Cameron <jic23@kernel.org>
To: Yulong Zhang <yulong.zhang@metoak.net>
Cc: linux-iio@vger.kernel.org, lars@metafoo.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/iio/iio_utils:fix memory leak
Date: Sat, 14 Jan 2023 16:41:14 +0000 [thread overview]
Message-ID: <20230114164114.3212921d@jic23-huawei> (raw)
In-Reply-To: <20230112110122.22973-1-yulong.zhang@metoak.net>
On Thu, 12 Jan 2023 19:01:22 +0800
Yulong Zhang <yulong.zhang@metoak.net> wrote:
> 1.fopen sysfsfp without fclose
> 2.asprintf filename without free
>
> Signed-off-by: Yulong Zhang <yulong.zhang@metoak.net>
Good spot. One suggestion below on how to tidy up the code
whilst fixing this.
> ---
> tools/iio/iio_utils.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/iio/iio_utils.c b/tools/iio/iio_utils.c
> index 8d35893b2..38e9352e5 100644
> --- a/tools/iio/iio_utils.c
> +++ b/tools/iio/iio_utils.c
> @@ -264,6 +264,8 @@ int iioutils_get_param_float(float *output, const char *param_name,
> if (fscanf(sysfsfp, "%f", output) != 1)
> ret = errno ? -errno : -ENODATA;
>
> + fclose(sysfsfp);
> +
> break;
> }
> error_free_filename:
> @@ -444,6 +446,7 @@ int build_channel_array(const char *device_dir, int buffer_idx,
> count--;
> goto error_cleanup_array;
> }
> + free(filename);
Instead of doing it here, why not move the free as early as possible (and hence
drop the need to do it in most of the error paths.
sysfsfp = fopen(filename, "r");
+ free(filename);
if (!sysfsfp) {
ret = -errno;
- free(filename)
... and the other cases that follow.
The same could be done for the case below, at the minor cost of not
having the filename for the print statement (which I think would be fine).
>
> ret = asprintf(&filename,
> "%s/%s_index",
next prev parent reply other threads:[~2023-01-14 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 11:01 [PATCH] tools/iio/iio_utils:fix memory leak Yulong Zhang
2023-01-14 16:41 ` Jonathan Cameron [this message]
2023-01-16 3:30 ` [PATCH v2] " Yulong Zhang
2023-01-16 15:16 ` Jonathan Cameron
2023-01-17 2:51 ` [PATCH v3] " Yulong Zhang
2023-01-21 17:53 ` Jonathan Cameron
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=20230114164114.3212921d@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yulong.zhang@metoak.net \
/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