From: "Lidong Yan via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>,
Lidong Yan <502024330056@smail.nju.edu.cn>,
Lidong Yan <502024330056@smail.nju.edu.cn>
Subject: [PATCH v2] fill_oids_from_packs: fix memory leak when fill_oids_from_packs failed
Date: Fri, 09 May 2025 07:14:28 +0000 [thread overview]
Message-ID: <pull.1957.v2.git.git.1746774869081.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1957.git.git.1746712275566.gitgitgadget@gmail.com>
From: Lidong Yan <502024330056@smail.nju.edu.cn>
In commit-graph.c:fill_oids_from_packs, if open_pack_index failed,
memory allocated and returned by add_packed_git will leak. Simply
add close_pack and free(p) will solve this problem.
Signed-off-by: Lidong Yan <502024330056@smail.nju.edu.cn>
---
fill_oids_from_packs: fix memory leak when fill_oids_from_packs failed
In commit-graph.c line 1930, if open_pack_index failed, memory allocated
in line 1925 by add_packed_git will leak. Simply add close_pack and
free(p) will solve this problem.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1957%2Fbrandb97%2Ffix-commit-graph-leak-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1957/brandb97/fix-commit-graph-leak-v2
Pull-Request: https://github.com/git/git/pull/1957
Range-diff vs v1:
1: 72402abe900 ! 1: 190961fe942 fill_oids_from_packs: fix memory leak when fill_oids_from_packs failed
@@ Metadata
## Commit message ##
fill_oids_from_packs: fix memory leak when fill_oids_from_packs failed
- In commit-graph.c line 1930, if open_pack_index failed, memory allocated
- in line 1925 by add_packed_git will leak. Simply add close_pack and
- free(p) will solve this problem.
+ In commit-graph.c:fill_oids_from_packs, if open_pack_index failed,
+ memory allocated and returned by add_packed_git will leak. Simply
+ add close_pack and free(p) will solve this problem.
Signed-off-by: Lidong Yan <502024330056@smail.nju.edu.cn>
commit-graph.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/commit-graph.c b/commit-graph.c
index 6394752b0b0..93d867770b0 100644
--- a/commit-graph.c
+++ b/commit-graph.c
@@ -1929,6 +1929,8 @@ static int fill_oids_from_packs(struct write_commit_graph_context *ctx,
}
if (open_pack_index(p)) {
ret = error(_("error opening index for %s"), packname.buf);
+ close_pack(p);
+ free(p);
goto cleanup;
}
for_each_object_in_pack(p, add_packed_commits, ctx,
base-commit: 6f84262c44a89851c3ae5a6e4c1a9d06b2068d75
--
gitgitgadget
next prev parent reply other threads:[~2025-05-09 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 13:51 [PATCH] fill_oids_from_packs: fix memory leak when fill_oids_from_packs failed Lidong Yan via GitGitGadget
2025-05-09 5:38 ` Patrick Steinhardt
2025-05-09 7:06 ` lidongyan
2025-05-09 7:14 ` Lidong Yan via GitGitGadget [this message]
2025-05-09 8:25 ` [PATCH v2] " Patrick Steinhardt
2025-05-09 8:30 ` [PATCH v3] commit-grap: fix memory leak when `fill_oids_from_packs()` fails Lidong Yan via GitGitGadget
2025-05-15 21:56 ` Junio C Hamano
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=pull.1957.v2.git.git.1746774869081.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=502024330056@smail.nju.edu.cn \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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).