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

[PATCH v2 1/3] read-cache: plug a few leaks

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 30, 2013, 13:34 UTC
Message-ID
<1369920861-30030-2-git-send-email-felipe.contreras@gmail.com>
In-Reply-To
<1369920861-30030-1-git-send-email-felipe.contreras@gmail.com>
We don't free 'istate->cache' properly.

Apparently 'initialized' doesn't really mean initialized, but loaded, or rather 'not-empty', and the cache can be used even if it's not 'initialized', so we can't rely on this variable to keep track of the 'istate->cache'.

So assume it always has data, and free it before overwriting it.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
 read-cache.c | 4 ++++
 1 file changed, 4 insertions(+)
diff --git a/read-cache.c b/read-cache.c
index 04ed561..e5dc96f 100644
--- a/read-cache.c
+++ b/read-cache.c
@@ -1449,6 +1449,7 @@ int read_index_from(struct index_state *istate, const char *path)
 	istate->version = ntohl(hdr->hdr_version);
 	istate->cache_nr = ntohl(hdr->hdr_entries);
 	istate->cache_alloc = alloc_nr(istate->cache_nr);
+	free(istate->cache);
 	istate->cache = xcalloc(istate->cache_alloc, sizeof(struct cache_entry *));
 	istate->initialized = 1;
 
@@ -1510,6 +1511,9 @@ int discard_index(struct index_state *istate)
 
 	for (i = 0; i < istate->cache_nr; i++)
 		free(istate->cache[i]);
+	free(istate->cache);
+	istate->cache = NULL;
+	istate->cache_alloc = 0;
 	resolve_undo_clear_index(istate);
 	istate->cache_nr = 0;
 	istate->cache_changed = 0;
-- 
1.8.3.rc3.312.g47657de
Previous: Felipe ContrerasNext: René Scharfe
Message 2 of 9 in “cherry-pick: fix memory leaks”
  1. 0/3 cherry-pick: fix memory leaksFelipe Contreras, May 30, 2013
  2. 1/3 read-cache: plug a few leaksFelipe Contreras, May 30, 2013
  3. René ScharfeMay 30, 2013
  4. Felipe ContrerasMay 31, 2013
  5. Felipe ContrerasMay 31, 2013
  6. 2/3 unpack-trees: plug a memory leakFelipe Contreras, May 30, 2013
  7. Stefano LattariniMay 30, 2013
  8. 3/3 unpack-trees: free created cache entriesFelipe Contreras, May 30, 2013
  9. René ScharfeMay 30, 2013

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.