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>
Subject: [PATCH v3 0/2] reftable/writer: fix memory leak when write fails
Date: Mon, 12 May 2025 12:49:02 +0000 [thread overview]
Message-ID: <pull.1958.v3.git.git.1747054145.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1958.v2.git.git.1746980165245.gitgitgadget@gmail.com>
Lidong Yan (2):
reftable/writer: fix memory leak when `padded_write()` fails
reftable/writer: fix memory leak when `writer_index_hash()` fails
reftable/writer.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
base-commit: 6f84262c44a89851c3ae5a6e4c1a9d06b2068d75
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1958%2Fbrandb97%2Ffix-reftable-padded-write-leak-v3
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1958/brandb97/fix-reftable-padded-write-leak-v3
Pull-Request: https://github.com/git/git/pull/1958
Range-diff vs v2:
1: 9329ae2d478 ! 1: 13ebdd672ff reftable/writer: fix memory leak if write fails
@@ Metadata
Author: Lidong Yan <502024330056@smail.nju.edu.cn>
## Commit message ##
- reftable/writer: fix memory leak if write fails
+ reftable/writer: fix memory leak when `padded_write()` fails
In reftable/writer.c:padded_write(), if w->writer failed, zeroed
allocated in `reftable_calloc` will leak. w->writer could be
@@ Commit message
some write error. Simply add reftable_free(zeroed) will solve this
problem.
- In reftable/writer.c:writer_index_hash(), if `reftable_buf_add` failed,
- key allocated by `reftable_malloc` will not be insert into `obj_index_tree`
- thus leaks. Simple add reftable_free(key) will solve this problem.
-
Signed-off-by: Lidong Yan <502024330056@smail.nju.edu.cn>
## reftable/writer.c ##
@@ reftable/writer.c: static int padded_write(struct reftable_writer *w, uint8_t *d
w->pending_padding = 0;
reftable_free(zeroed);
-@@ reftable/writer.c: static int writer_index_hash(struct reftable_writer *w, struct reftable_buf *has
-
- reftable_buf_reset(&key->hash);
- err = reftable_buf_add(&key->hash, hash->buf, hash->len);
-- if (err < 0)
-+ if (err < 0) {
-+ reftable_free(key);
- return err;
-+ }
- tree_insert(&w->obj_index_tree, key,
- &obj_index_tree_node_compare);
- } else {
-: ----------- > 2: 64f778ce2ba reftable/writer: fix memory leak when `writer_index_hash()` fails
--
gitgitgadget
next prev parent reply other threads:[~2025-05-12 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 3:50 [PATCH] reftable/writer: fix memory leak when `padded_write()` fails Lidong Yan via GitGitGadget
2025-05-11 16:16 ` [PATCH v2] reftable/writer: fix memory leak if write fails Lidong Yan via GitGitGadget
2025-05-12 8:25 ` Patrick Steinhardt
2025-05-12 10:54 ` lidongyan
2025-05-12 12:49 ` Lidong Yan via GitGitGadget [this message]
2025-05-12 12:49 ` [PATCH v3 1/2] reftable/writer: fix memory leak when `padded_write()` fails Lidong Yan via GitGitGadget
2025-05-12 12:49 ` [PATCH v3 2/2] reftable/writer: fix memory leak when `writer_index_hash()` fails Lidong Yan via GitGitGadget
2025-05-12 14:34 ` [PATCH v3 0/2] reftable/writer: fix memory leak when write fails Patrick Steinhardt
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.1958.v3.git.git.1747054145.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).