git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: "dmh@ucar.edu" <dmh@ucar.edu>, git@vger.kernel.org
Subject: Re: [PATCH 2/5] common-main: call git_extract_argv0_path()
Date: Fri, 1 Jul 2016 10:05:19 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1607011000320.12947@virtualbox> (raw)
In-Reply-To: <20160701060404.GB4593@sigill.intra.peff.net>

Hi Peff,

On Fri, 1 Jul 2016, Jeff King wrote:

> This has been an accident-waiting-to-happen for a long time,
> but wasn't triggered until recently because it involves one
> of those programs actually calling system_path(). That
> happened with git-credential-store in v2.8.0 with ae5f677
> (lazily load core.sharedrepository, 2016-03-11). The
> program:
> 
>   - takes a lock file, which...
> 
>   - opens a tempfile, which...
> 
>   - calls adjust_shared_perm to fix permissions, which...
> 
>   - lazy-loads the config (as of ae5f677), which...
> 
>   - calls system_path() to find the location of
>     /etc/gitconfig
> 
> On systems with RUNTIME_PREFIX, this means credential-store
> reliably hits that assert() and cannot be used.

Thank you for that thorough write-up. I am now even more upset that we had
to go through the same steps (it took me an hour to figure out what was
going wrong, mostly due to abort() *not* spitting out a stack trace, so I
had to wield some gdb magic).

I am partly to blame here, of course, because I did not report what I did
to this mailing list. But then: 1) I considered this a Windows-only
problem, and 2) I was really already swamped, as it were.

The patch is good, of course, as are the rest of the patches (I did not
really look at them very thoroughly, but then, they are pretty obvious
improvements).

Ciao,
Dscho

  reply	other threads:[~2016-07-01  8:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 21:24 git-credentials-store.exe crash dmh
2016-07-01  4:07 ` Jeff King
2016-07-01  5:55   ` [PATCH 0/5] consistent setup code for external commands Jeff King
2016-07-01  5:58     ` [PATCH 1/5] add an extra level of indirection to main() Jeff King
2016-07-01  8:04       ` Johannes Schindelin
2016-07-01  8:19         ` Jeff King
2016-07-01 13:39           ` Johannes Schindelin
2016-07-01 22:38             ` Jeff King
2016-07-02  6:52               ` Johannes Schindelin
2016-07-01  6:04     ` [PATCH 2/5] common-main: call git_extract_argv0_path() Jeff King
2016-07-01  8:05       ` Johannes Schindelin [this message]
2016-07-01  6:06     ` [PATCH 3/5] common-main: call sanitize_stdfds() Jeff King
2016-07-01  6:06     ` [PATCH 4/5] common-main: call restore_sigpipe_to_default() Jeff King
2016-07-01  6:07     ` [PATCH 5/5] common-main: call git_setup_gettext() Jeff King
2016-07-01  7:45     ` [PATCH 0/5] consistent setup code for external commands Johannes Schindelin
2016-07-01 22:19     ` Junio C Hamano
2016-07-01 22:39       ` Jeff King
2016-07-06 15:17         ` Junio C Hamano
2016-07-06 15:36           ` Johannes Schindelin
2016-07-01  7:38   ` git-credentials-store.exe crash Johannes Schindelin
2016-07-01  7:43     ` Jeff King

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=alpine.DEB.2.20.1607011000320.12947@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=dmh@ucar.edu \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).