From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Tianjia Zhang" <tianjia.zhang@linux.alibaba.com>,
"David Howells" <dhowells@redhat.com>,
"David Woodhouse" <dwmw2@infradead.org>,
<keyrings@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sign-file: fix memory leak
Date: Fri, 09 Jun 2023 20:45:17 +0300 [thread overview]
Message-ID: <CT8B23KI5MSP.2RS13WHU6LH7J@suppilovahvero> (raw)
In-Reply-To: <20230525084324.56718-1-tianjia.zhang@linux.alibaba.com>
On Thu May 25, 2023 at 11:43 AM EEST, Tianjia Zhang wrote:
> The buffer allocated by asprintf() must be freeed.
... and it is freed by do_exit().
Short summary should really be
"sign-file: Explicitly call free(sig_file_name)"
David, what do you think of this patch is general?
Again, as an independent patch it is not really doing much at all.
Since freeing resources is a good practice, it would make sense as
a step toward doing something functionally interesting.
> Signed-off-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
> ---
> scripts/sign-file.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/sign-file.c b/scripts/sign-file.c
> index b90fc9f7437f..94267cf72197 100644
> --- a/scripts/sign-file.c
> +++ b/scripts/sign-file.c
> @@ -369,6 +369,7 @@ int main(int argc, char **argv)
> "%s", sig_file_name);
> #endif
> BIO_free(b);
> + free(sig_file_name);
> }
>
> if (sign_only) {
> @@ -420,8 +421,10 @@ int main(int argc, char **argv)
> ERR(BIO_free(bd) < 0, "%s", dest_name);
>
> /* Finally, if we're signing in place, replace the original. */
> - if (replace_orig)
> + if (replace_orig) {
> ERR(rename(dest_name, module_name) < 0, "%s", dest_name);
> + free(dest_name);
> + }
>
> return 0;
> }
> --
> 2.24.3 (Apple Git-128)
BR, Jarkko
prev parent reply other threads:[~2023-06-09 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 8:43 Tianjia Zhang
2023-06-09 17:45 ` Jarkko Sakkinen [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=CT8B23KI5MSP.2RS13WHU6LH7J@suppilovahvero \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tianjia.zhang@linux.alibaba.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
all inboxes | Powered by JetHome®