git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* Bug: Commit a merge resolution with non-closed conflict markers leads to errs, segfault
@ 2021-07-22  9:28 BENTZ Sylvain
  2021-07-22 10:25 ` Felipe Contreras
  0 siblings, 1 reply; 4+ messages in thread
From: BENTZ Sylvain @ 2021-07-22  9:28 UTC (permalink / raw)
  To: git

Hello,

I've stumbled on a segmentation fault while resolving merge conflicts.
Basically, I missed to remove some conflict markers, tried to commit the
(faulty) merge resolution, and Git mishandles that.

The original issue happened applying a patch using 3-way merge.  The minimal
working example below creates a conflict with a simple `git merge` command.


Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

1. Create a merge conflict
2. Edit the conflicted file, keep some conflict markers (more on that below [1])
3. Commit (works but errors are reported!)
4. Fix the file, by removing all conflict markers
5. Commit (works but segmentation fault!)
6. Commit again, with some changes or with an empty commit (fatal error!)

See shell script (MWE) below [2].


What did you expect to happen? (Expected behavior)

At step 3, Git should return an error without committing.


What happened instead? (Actual behavior)

Git works and breaks at the same time.
Step 3 : It throws error messages without returning an error, and it does commit.
Step 5 : It breaks (segfault), manages to commit, but fails to remove a lockfile.

See terminal output below [3].

Then, if I reset hard to the commit named "master", delete the lockfile, and
repeat the process, I still get errors in step 3, but no segfault in step 5.


What's different between what you expected and what actually happened?

Git shouldn't segfault obviously. See gdb output below [4].


Anything else you want to add:

Tested versions: 2.20 (debian stable), 2.32 (alpine 3.14), next (alpine 3.14)

[1] Some configurations of conflict markers triggers that bug, others don't.
    The minimal working example shows the case (A).

Failure cases:
(A)        (B)        (C)
<<<<<<<<<  <<<<<<<<<  <<<<<<<<<
           >>>>>>>>>  =========

Not failure cases:
(D)        (E)        (F)
=========  =========  >>>>>>>>>
>>>>>>>>>                      

[2] Shell script (MWE)

# Setup conflicting branches `master' and `conflict'

FOLDER=${1:-git-break}
mkdir "$FOLDER"
cd "$FOLDER"
git init
echo '' > README
git add README
git commit -m "First commit"
echo master > README
git commit -i README -m "master"
git checkout -b conflict HEAD~
echo conflict > README
git commit -i README -m "conflict"
git checkout master

# Convenience functions

mer() { set -x; git merge conflict; }
com() { set -x; git add README; git commit -m "$1"; }
del() { set -x; for arg; do sed -i "/$arg/ d" README; done; cat README; }
see() { set -x; git log -p -n2; }

# Script

mer                  # Create a merge conflict
del = '>'            # Keep the conflict marker `<<<<<<<<<<<'
com "Merge commit"   # Commit (errors reported)
del '<'              # Fix by deleting the remaining marker
com "Fix the merge"  # Commit (segfault)
echo next >> README  # Do some changes...
com "next"           # Commit (fatal error)

[3] Terminal output

####### START TERMINAL OUTPUT ########

/git-min # see
+ see
+ set -x
+ git log -p -n2
commit 9a9dd03509b8cf45c8037c60c256d6ef67f9e431 (HEAD -> master)
Author: sylvain.bentz <sylvain.bentz@md6.fr>
Date:   Wed Jul 21 14:50:37 2021 +0200

    master

diff --git a/README b/README
index 8b13789..1f7391f 100644
--- a/README
+++ b/README
@@ -1 +1 @@
-
+master

commit cfb5d5cd9f28e1dcca7a1d1088405d8ec4ebf713
Author: sylvain.bentz <sylvain.bentz@md6.fr>
Date:   Wed Jul 21 14:49:36 2021 +0200

    First commit

diff --git a/README b/README
new file mode 100644
index 0000000..8b13789
--- /dev/null
+++ b/README
@@ -0,0 +1 @@
+

/git-min # mer
+ mer
+ set -x
+ git merge conflict
Auto-merging README
CONFLICT (content): Merge conflict in README
Recorded preimage for 'README'
Automatic merge failed; fix conflicts and then commit the result.

/git-min # del = '>'
+ del '=' '>'
+ set -x
+ sed -i '/=/ d' README
+ sed -i '/>/ d' README
+ cat README
<<<<<<< HEAD
master
conflict

/git-min # com merge
+ com merge
+ set -x
+ git add README
+ git commit -m merge
error: could not parse conflict hunks in 'README'
error: could not parse conflict hunks in 'README'
Recorded preimage for 'README'
[master ab6c525] merge

/git-min # del '<'
+ del '<'
+ set -x
+ sed -i '/</ d' README
+ cat README
master
conflict

/git-min # com mergefix
+ com mergefix
+ set -x
+ git add README
+ git commit -m mergefix
Segmentation fault

/git-min # see
+ see
+ set -x
+ git log -p -n2
commit 8ea1a55602ba5ae505b43f2ae3a49b3a9a26b2fe (HEAD -> master)
Author: Your Name <you@example.com>
Date:   Wed Jul 21 15:38:35 2021 +0000

    mergefix

diff --git a/README b/README
index 59c1bc9..6ecc231 100644
--- a/README
+++ b/README
@@ -1,3 +1,2 @@
-<<<<<<< HEAD
 master
 conflict

commit ab6c52591506ac2e75745814527f062d767b4e11
Merge: 9a9dd03 42a166a
Author: Your Name <you@example.com>
Date:   Wed Jul 21 15:38:18 2021 +0000

    merge

/git-min # echo 'next' >> README
+ echo next

/git-min # com next
+ com next
+ set -x
+ git add README
+ git commit -m next
fatal: Unable to create '/git-min/.git/MERGE_RR.lock': File exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.

/git-min # git --version
+ git --version
git version 2.32.0.473.g1bb01aad6f

/git-min # git config --list
+ git config --list
user.email=you@example.com
user.name=Your Name
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
core.pager=cat
color.ui=never

####### END TERMINAL OUTPUT ########

[4] GDB Output

(gdb) run
Starting program: /usr/local/bin/git commit -m Fix\ the\ merge
warning: Error disabling address space randomization: Operation not permitted

Program received signal SIGSEGV, Segmentation fault.
0x000055dbdff61748 in do_rerere_one_path (update=0x7ffffce68720, rr_item=0x7f5ed8e20340,
    istate=0x55dbe00ef520 <the_index>) at rerere.c:736
736


Please review the rest of the bug report below.
You can delete any lines you don't wish to share.

[System Info]
git version:
git version 2.32.0.473.g1bb01aad6f
cpu: x86_64
built from commit: 1bb01aad6fdafaac7a11bed18a67384f28ab735b
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64
compiler info: gnuc: 10.3
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>

[Enabled Hooks]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Bug: Commit a merge resolution with non-closed conflict markers leads to errs, segfault
  2021-07-22  9:28 Bug: Commit a merge resolution with non-closed conflict markers leads to errs, segfault BENTZ Sylvain
@ 2021-07-22 10:25 ` Felipe Contreras
  2021-07-22 12:53   ` BENTZ Sylvain
  0 siblings, 1 reply; 4+ messages in thread
From: Felipe Contreras @ 2021-07-22 10:25 UTC (permalink / raw)
  To: BENTZ Sylvain, git

BENTZ Sylvain wrote:
> I've stumbled on a segmentation fault while resolving merge conflicts.
> Basically, I missed to remove some conflict markers, tried to commit the
> (faulty) merge resolution, and Git mishandles that.
> 
> The original issue happened applying a patch using 3-way merge.  The minimal
> working example below creates a conflict with a simple `git merge` command.

A quick workaround:

  git config --global rerere.enabled false

But yeah, there seems to be a bug in `git rerere`.

-- 
Felipe Contreras

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Bug: Commit a merge resolution with non-closed conflict markers leads to errs, segfault
  2021-07-22 10:25 ` Felipe Contreras
@ 2021-07-22 12:53   ` BENTZ Sylvain
  2021-07-22 14:17     ` Ævar Arnfjörð Bjarmason
  0 siblings, 1 reply; 4+ messages in thread
From: BENTZ Sylvain @ 2021-07-22 12:53 UTC (permalink / raw)
  To: Felipe Contreras, git

Oh I wasn't aware of this when I initialized my MWE repo, from git-config[1]:

  By default, git-rerere[1] is enabled if there is an rr-cache directory under
  the $GIT_DIR, e.g. if "rerere" was previously used in the repository.

The correct MWE requires to enable rerere:

  git config rerere.enabled true

--
Sylvain Bentz

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Bug: Commit a merge resolution with non-closed conflict markers leads to errs, segfault
  2021-07-22 12:53   ` BENTZ Sylvain
@ 2021-07-22 14:17     ` Ævar Arnfjörð Bjarmason
  0 siblings, 0 replies; 4+ messages in thread
From: Ævar Arnfjörð Bjarmason @ 2021-07-22 14:17 UTC (permalink / raw)
  To: BENTZ Sylvain; +Cc: Felipe Contreras, git


On Thu, Jul 22 2021, BENTZ Sylvain wrote:

> Oh I wasn't aware of this when I initialized my MWE repo, from git-config[1]:
>
>   By default, git-rerere[1] is enabled if there is an rr-cache directory under
>   the $GIT_DIR, e.g. if "rerere" was previously used in the repository.
>
> The correct MWE requires to enable rerere:
>
>   git config rerere.enabled true

I think the patch I posted at the end of
https://lore.kernel.org/git/87v96p4w3f.fsf@evledraar.gmail.com/ should
might catch this, i.e. the "could not copy" error.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-07-22 14:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-22  9:28 Bug: Commit a merge resolution with non-closed conflict markers leads to errs, segfault BENTZ Sylvain
2021-07-22 10:25 ` Felipe Contreras
2021-07-22 12:53   ` BENTZ Sylvain
2021-07-22 14:17     ` Ævar Arnfjörð Bjarmason

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.version-control.git
	nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.version-control.git
	nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git