From: Junio C Hamano <gitster@pobox.com>
To: "Lidong Yan via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Lidong Yan <502024330056@smail.nju.edu.cn>
Subject: Re: [PATCH] builtin/am: fix memory leak in `split_mail_stgit_series`
Date: Mon, 12 May 2025 07:02:08 -0700 [thread overview]
Message-ID: <xmqqikm6vsf3.fsf@gitster.g> (raw)
In-Reply-To: <pull.1961.git.git.1747015647505.gitgitgadget@gmail.com> (Lidong Yan via GitGitGadget's message of "Mon, 12 May 2025 02:07:27 +0000")
"Lidong Yan via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Lidong Yan <502024330056@smail.nju.edu.cn>
>
> In builtin/am.c:split_mail_stgit_series, if `fopen` failed,
> `series_dir_buf` allocated by `xstrdup` will leak. Add `free` in
> `!fp` if branch will prevent the leak.
>
> diff --git a/builtin/am.c b/builtin/am.c
> index 4afb519830f..e32a3b4c973 100644
> --- a/builtin/am.c
> +++ b/builtin/am.c
> @@ -850,8 +850,10 @@ static int split_mail_stgit_series(struct am_state *state, const char **paths,
> series_dir = dirname(series_dir_buf);
>
> fp = fopen(*paths, "r");
> - if (!fp)
> + if (!fp) {
> + free(series_dir_buf);
> return error_errno(_("could not open '%s' for reading"), *paths);
> + }
>
> while (!strbuf_getline_lf(&sb, fp)) {
> if (*sb.buf == '#')
>
> base-commit: 6f84262c44a89851c3ae5a6e4c1a9d06b2068d75
Obviously correct; will queue. Thanks.
prev parent reply other threads:[~2025-05-12 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 2:07 [PATCH] builtin/am: fix memory leak in `split_mail_stgit_series` Lidong Yan via GitGitGadget
2025-05-12 8:10 ` Patrick Steinhardt
2025-05-12 14:02 ` Junio C Hamano [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=xmqqikm6vsf3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=502024330056@smail.nju.edu.cn \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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).