diff options
author | Jeff King <peff@peff.net> | 2017-05-25 15:33:05 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-05-26 12:51:06 +0900 |
commit | ef4fe5617eadc24fd09ce7778b77bb87f147480c (patch) | |
tree | 83aec44a41bc665699ca91c5f4ee96ec0cdbb5c9 /t/t5518-fetch-exit-status.sh | |
parent | Git 2.12.3 (diff) | |
download | tgif-ef4fe5617eadc24fd09ce7778b77bb87f147480c.tar.xz |
connect.c: fix leak in parse_one_symref_info()
If we successfully parse a symref value like
"HEAD:refs/heads/master", we add the result to a string
list. But because the string list is marked
STRING_LIST_INIT_DUP, the string list code will make a copy
of the string and add the copy.
This patch fixes it by adding the entry with
string_list_append_nodup(), which lets the string list take
ownership of our newly allocated string. There are two
alternatives that seem like they would work, but aren't the
right solution.
The first is to initialize the list with the "NODUP"
initializer. That would avoid the copy, but then the string
list would not realize that it owns the strings. When we
eventually call string_list_clear(), it would not free the
strings, causing a leak.
The second option would be to use the normal
string_list_append(), but free the local copy in our
function. We can't do this because the local copy actually
contains _two_ strings; the symref name and its target. We
point to the target pointer via the "util" field, and its
memory must last as long as the string list does.
You may also wonder whether it's safe to ever free the local
copy, since the target points into it. The answer is yes,
because we duplicate it in annotaate_refs_with_symref_info
before clearing the string list.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5518-fetch-exit-status.sh')
0 files changed, 0 insertions, 0 deletions