diff options
author | Elijah Newren <newren@gmail.com> | 2023-04-22 20:22:10 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2023-04-24 14:04:07 -0700 |
commit | 000c4ceca794645eb4744f9c9afb6247232c0646 (patch) | |
tree | d6c9f4ca4b1ed0d652bcb99812d1bc14dab5ff4e /commit.c | |
parent | 7556e5d737b917d31ac3729b0f5e2391da7e132a (diff) |
merge-ort: fix calling merge_finalize() with no intermediate merge
If some code sets up the data structures for a merge, but then never
actually performs one before calling merge_finalize(), then
merge_finalize() wouldn't notice that result->priv was NULL and
return early, resulting in following that NULL pointer and getting
a segfault. There is currently no code in the git codebase that does
this, but this issue was found during testing of some proposed patches
that had the following structure:
struct merge_options merge_opt;
struct merge_result result;
init_merge_options(&merge_opt, the_repository);
memset(&result, 0, sizeof(result));
<do N merges, for some value of N>
merge_finalize(&merge_opt, &result);
where some flags could cause the code to have N=0, i.e. doing no merges.
Add a check for result->priv being NULL and return early to avoid a
segfault in these kinds of cases.
While at it, ensure the FREE_AND_NULL() in the function does something
useful with the nulling aspect, namely sets result->priv to NULL rather
than a mere temporary.
Reported-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions