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

[PATCHv4 1/4] notes: don't leak memory in git_config_get_notes_strategy

From
Stefan Beller <sbeller@google.com>
Date
Apr 1, 2016, 00:35 UTC
Message-ID
<1459470946-16522-2-git-send-email-sbeller@google.com>
In-Reply-To
<1459470946-16522-1-git-send-email-sbeller@google.com>

`value` is just a temporary scratchpad, so we need to make sure it doesn't leak. It is xstrdup'd in `git_config_get_string_const` and `parse_notes_merge_strategy` just compares the string against predefined values, so no need to keep it around longer.

Signed-off-by: Stefan Beller <sbeller@google.com>
---
 builtin/notes.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/builtin/notes.c b/builtin/notes.c
index 52aa9af..afcfa8f 100644
--- a/builtin/notes.c
+++ b/builtin/notes.c
@@ -741,13 +741,14 @@ static int merge_commit(struct notes_merge_options *o)
 static int git_config_get_notes_strategy(const char *key,
 					 enum notes_merge_strategy *strategy)
 {
-	const char *value;
+	char *value;
 
-	if (git_config_get_string_const(key, &value))
+	if (git_config_get_string(key, &value))
 		return 1;
 	if (parse_notes_merge_strategy(value, strategy))
 		git_die_config(key, "unknown notes merge strategy %s", value);
 
+	free(value);
 	return 0;
 }
 
-- 
2.5.0.264.gc776916.dirty
Previous: Stefan BellerNext: Eric Sunshine
Message 2 of 14 in “[PATCHv4 0/4] Some cleanups”
  1. Stefan BellerApr 1, 2016
  2. 1/4 notes: don't leak memory in git_config_get_notes_strategyStefan Beller, Apr 1, 2016
  3. Eric SunshineApr 1, 2016
  4. Junio C HamanoApr 1, 2016
  5. Junio C HamanoApr 1, 2016
  6. Jeff KingApr 1, 2016
  7. Eric SunshineApr 1, 2016
  8. 2/4 abbrev_sha1_in_line: don't leak memoryStefan Beller, Apr 1, 2016
  9. 3/4 bundle: don't leak an fd in case of early returnStefan Beller, Apr 1, 2016
  10. Junio C HamanoApr 1, 2016
  11. Jeff KingApr 1, 2016
  12. Junio C HamanoApr 1, 2016
  13. Jeff KingApr 1, 2016
  14. 4/4 credential-cache, send_request: close fd when doneStefan Beller, Apr 1, 2016

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.