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

[PATCH v2] merge-ort: fix calling merge_finalize() with no intermediate merge

From
Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>
Date
Apr 22, 2023, 20:22 UTC
Message-ID
<pull.1518.v2.git.1682194930766.gitgitgadget@gmail.com>
In-Reply-To
<pull.1518.git.1681974847078.gitgitgadget@gmail.com>
From: Elijah Newren <newren@gmail.com>

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>
---
    merge-ort: fix calling merge_finalize() with no intermediate merge
    
    Changes since v1:
    
     * Moved code into an if-block instead of returning early, as suggested
       by Stolee.
    
    See
    https://lore.kernel.org/git/CABPp-BHCdjOutYqdMO1NbYKNA0BgkXRgwUEKK=MX0kXM-5G_DQ@mail.gmail.com/
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1518%2Fnewren%2Ffix-merge-finalize-with-no-merge-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1518/newren/fix-merge-finalize-with-no-merge-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/1518
Range-diff vs v1:
 1:  e636027f60c ! 1:  2cb1c63f05b merge-ort: fix calling merge_finalize() with no intermediate merge
     @@ merge-ort.c: void merge_switch_to_result(struct merge_options *opt,
       
      -	clear_or_reinit_internal_opts(opti, 0);
      -	FREE_AND_NULL(opti);
     -+	if (!result->priv)
     -+		return;
     -+	clear_or_reinit_internal_opts(result->priv, 0);
     -+	FREE_AND_NULL(result->priv);
     ++	if (result->priv) {
     ++		clear_or_reinit_internal_opts(result->priv, 0);
     ++		FREE_AND_NULL(result->priv);
     ++	}
       }
       
       /*** Function Grouping: helper functions for merge_incore_*() ***/
 merge-ort.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/merge-ort.c b/merge-ort.c
index 5bf64354d16..29966fc082f 100644
--- a/merge-ort.c
+++ b/merge-ort.c
@@ -4718,14 +4718,14 @@ void merge_switch_to_result(struct merge_options *opt,
 void merge_finalize(struct merge_options *opt,
 		    struct merge_result *result)
 {
-	struct merge_options_internal *opti = result->priv;
-
 	if (opt->renormalize)
 		git_attr_set_direction(GIT_ATTR_CHECKIN);
 	assert(opt->priv == NULL);
 
-	clear_or_reinit_internal_opts(opti, 0);
-	FREE_AND_NULL(opti);
+	if (result->priv) {
+		clear_or_reinit_internal_opts(result->priv, 0);
+		FREE_AND_NULL(result->priv);
+	}
 }
 
 /*** Function Grouping: helper functions for merge_incore_*() ***/

base-commit: 667fcf4e15379790f0b609d6a83d578e69f20301
-- 
gitgitgadget
Previous: Junio C HamanoNext: Derrick Stolee
Message 6 of 7 in “merge-ort: fix calling merge_finalize() with no intermediate merge”
  1. merge-ort: fix calling merge_finalize() with no intermediate mergeElijah Newren via GitGitGadget, Apr 20, 2023
  2. Derrick StoleeApr 20, 2023
  3. Junio C HamanoApr 20, 2023
  4. Elijah NewrenApr 22, 2023
  5. Junio C HamanoApr 20, 2023
  6. merge-ort: fix calling merge_finalize() with no intermediate mergeElijah Newren via GitGitGadget, Apr 22, 2023
  7. Derrick StoleeApr 24, 2023

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.