git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Jeff King <peff@peff.net>, Aleksey Midenkov <midenok@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Bug: fatal: Unable to create '.../.git/index.lock': File exists.
Date: Fri, 3 May 2019 11:47:23 +0200 (DST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1905031146490.45@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CACsJy8D7bx46bix_LmGr=xcwsrA=LehXmLmnONLz2w3q6f80vw@mail.gmail.com>

Hi Duy,

On Fri, 3 May 2019, Duy Nguyen wrote:

> I have a feeling that most operations read the index unlocked,
> manipulate and only lock before writing things out. So yeah it's
> probably already racy.

IIRC there is a check for that, so it is not actually racy ;-)

Ciao,
Johannes

  reply	other threads:[~2019-05-03  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF8BazDu_GqoCPBQ-gEJ+q8n1aWSjf_TOV7bDE5VCQkDgBjyfQ@mail.gmail.com>
2019-04-29 11:02 ` Bug: fatal: Unable to create '.../.git/index.lock': File exists Aleksey Midenkov
2019-04-29 11:34   ` Duy Nguyen
2019-04-30 11:19     ` Aleksey Midenkov
2019-04-30 17:41       ` Jeff King
2019-05-01  7:15         ` Aleksey Midenkov
2019-05-01 18:36           ` Jeff King
2019-05-02 13:45             ` Aleksey Midenkov
2019-05-02 15:07               ` Jeff King
2019-05-02 16:38                 ` Duy Nguyen
2019-05-02 16:58                   ` Jeff King
2019-05-02 17:24                     ` Duy Nguyen
2019-05-03  9:47                       ` Johannes Schindelin [this message]
2019-05-03 10:22                         ` Duy Nguyen
2019-05-03  5:42                     ` Duy Nguyen
2019-04-29 21:10   ` Johannes Schindelin

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=nycvar.QRO.7.76.6.1905031146490.45@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=midenok@gmail.com \
    --cc=pclouds@gmail.com \
    --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).