diff options
author | Taylor Blau <me@ttaylorr.com> | 2019-09-05 18:04:55 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-09-09 10:55:58 -0700 |
commit | 16749b8dd2cd2d3ab693ac7ebe110e57cf054005 (patch) | |
tree | 03391aeeace7466d9fd6cee7422e29a75cb48d83 /t/t0060-path-utils.sh | |
parent | t/t5318: introduce failing 'git commit-graph write' tests (diff) | |
download | tgif-16749b8dd2cd2d3ab693ac7ebe110e57cf054005.tar.xz |
commit-graph.c: handle commit parsing errors
To write a commit graph chunk, 'write_graph_chunk_data()' takes a list
of commits to write and parses each one before writing the necessary
data, and continuing on to the next commit in the list.
Since the majority of these commits are not parsed ahead of time (an
exception is made for the *last* commit in the list, which is parsed
early within 'copy_oids_to_commits'), it is possible that calling
'parse_commit_no_graph()' on them may return an error. Failing to catch
these errors before de-referencing later calls can result in a undefined
memory access and a SIGSEGV.
One such example of this is 'get_commit_tree_oid()', which expects a
parsed object as its input (in this case, the commit-graph code passes
'*list'). If '*list' causes a parse error, the subsequent call will
fail.
Prevent such an issue by checking the return value of
'parse_commit_no_graph()' to avoid passing an unparsed object to a
function which expects a parsed object, thus preventing a segfault.
It is worth noting that this fix is really skirting around the issue in
object.c's 'parse_object()', which makes it difficult to tell how
corrupt an object is without digging into it. Presumably one could
change the meaning of 'parse_object' returns, but this would require
adjusting each callsite accordingly. Instead of that, add an additional
check to the object parsed.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t0060-path-utils.sh')
0 files changed, 0 insertions, 0 deletions