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

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

From
Lidong Yan via GitGitGadget <gitgitgadget@gmail.com>
Date
May 12, 2025, 12:49 UTC
Message-ID
<13ebdd672ff1a76ef684d9260b782c750c65ddba.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:padded_write(), if w->writer failed, zeroed allocated in `reftable_calloc` will leak. w->writer could be `reftable_write_data` in reftable/stack.c, and could fail due to some write error. Simply add reftable_free(zeroed) 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 cb16f71be49e..3ceb37428887 100644
--- a/reftable/writer.c
+++ b/reftable/writer.c
@@ -57,8 +57,10 @@ static int padded_write(struct reftable_writer *w, uint8_t *data, size_t len,
 			return -1;
 
 		n = w->write(w->write_arg, zeroed, w->pending_padding);
-		if (n < 0)
+		if (n < 0) {
+			reftable_free(zeroed);
 			return n;
+		}
 
 		w->pending_padding = 0;
 		reftable_free(zeroed);
-- 
gitgitgadget
Previous: Lidong Yan via GitGitGadgetNext: Lidong Yan via GitGitGadget
Message 6 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.