git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v3 2/2] reftable/writer: fix memory leak when `writer_index_hash()` fails

From
Lidong Yan via GitGitGadget <gitgitgadget@gmail.com>
Date
May 12, 2025, 12:49 UTC
Message-ID
<64f778ce2ba6a3010d284daeb09ed2d591b54565.1747054145.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.1958.v3.git.git.1747054145.gitgitgadget@gmail.com>
From: Lidong Yan <502024330056@smail.nju.edu.cn>

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 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/reftable/writer.c b/reftable/writer.c
index 3ceb37428887..3b4ebdd6dced 100644
--- a/reftable/writer.c
+++ b/reftable/writer.c
@@ -258,8 +258,10 @@ 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 {
-- 
gitgitgadget
Previous: Lidong Yan via GitGitGadgetNext: Patrick Steinhardt
Message 7 of 8 in “reftable/writer: fix memory leak when `padded_write()` fails”
  1. reftable/writer: fix memory leak when `padded_write()` failsLidong Yan via GitGitGadget, May 10, 2025
  2. reftable/writer: fix memory leak if write failsLidong Yan via GitGitGadget, May 11, 2025
  3. Patrick SteinhardtMay 12, 2025
  4. lidongyanMay 12, 2025
  5. 0/2 reftable/writer: fix memory leak when write failsLidong Yan via GitGitGadget, May 12, 2025
  6. 1/2 reftable/writer: fix memory leak when `padded_write()` failsLidong Yan via GitGitGadget, May 12, 2025
  7. 2/2 reftable/writer: fix memory leak when `writer_index_hash()` failsLidong Yan via GitGitGadget, May 12, 2025
  8. Patrick SteinhardtMay 12, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.