From: "Vusich, Joseph" <jvusich@amazon.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: bug: conflicting core.bare setting causes segfault during bare clone
Date: Wed, 3 Mar 2021 00:06:01 +0000 [thread overview]
Message-ID: <D99DD9AD-54E5-4357-BA50-8B9CAE23084E@amazon.com> (raw)
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)
$ env | grep GIT
$ git config --list
user.email=jvusich@amazon.com
user.name=Joseph Vusich
core.bare=false
$ git clone --bare https://github.com/josephvusich/fixture
Cloning into bare repository 'fixture.git'...
zsh: segmentation fault /opt/local/bin/git clone --bare https://github.com/josephvusich/fixture
What did you expect to happen? (Expected behavior)
"git clone --bare" should clone a bare repository, regardless of the core.bare setting in the global config
What happened instead? (Actual behavior)
"git clone --bare" causes a segfault if the global gitconfig has core.bare=false
Anything else you want to add:
* Non-bare clones still work when core.bare=false
* Bare clones only work when core.bare=true, or if core.bare is absent from gitconfig
* Started failing with Git 2.30.0, also fails on 2.30.1, but succeeds on 2.29.2
* Issue reproduced on multiple machines, running Ubuntu, Mac OS, and Alpine Linux
* Running with all TRACEs enabled shows only one additional line prior to "Cloning"
15:38:08.567292 git.c:444 trace: built-in: git clone --bare https://github.com/josephvusich/fixture
* The fixture.git directory is created prior to the segfault, the fixture.git/config file content is below:
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
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.30.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64 x86_64
compiler info: clang: 12.0.0 (clang-1200.0.32.2)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks]
not run from a git repository - no hooks to show
next reply other threads:[~2021-03-03 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 0:06 Vusich, Joseph [this message]
2021-03-03 23:59 ` bug: conflicting core.bare setting causes segfault during bare clone brian m. carlson
2021-03-04 1:13 ` Junio C Hamano
2021-03-04 11:48 ` Vusich, Joseph
2021-03-08 13:17 ` [PATCH] builtin/init-db: handle bare clones when core.bare set to false brian m. carlson
2021-03-08 16:43 ` Eric Sunshine
2021-03-08 23:22 ` brian m. carlson
2021-03-10 1:11 ` [PATCH v2] " brian m. carlson
2021-03-10 23:09 ` Junio C Hamano
2021-03-10 23:33 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D99DD9AD-54E5-4357-BA50-8B9CAE23084E@amazon.com \
--to=jvusich@amazon.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).