mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michal Suchanek <>
Cc: "Michal Suchanek" <>,
	"Eric Sunshine" <>,
	"Marketa Calabkova" <>,
	"Nguyễn Thái Ngọc Duy" <>,
	"Junio C Hamano" <>
Subject: [PATCH 0/2] worktree add race fix
Date: Mon, 18 Feb 2019 18:04:55 +0100	[thread overview]
Message-ID: <> (raw)


I am running a git automation script that crates a tree and commmits it into a
git repository repeatedly.

I noticed that the step which creates a tree is most time-consuming part of the
script and when a lot of data is to be automatically added to the repository it
is benefical to parallelize this part.

To do so I had the script create a dozen worktrees and share the work between
them. The problem is automatically creating several worktrees occasioanlly

The most common problem is in the worktree add implementation itself which
tries to find an available directory name and then mkdir() it. Of course, doing
that several times in parallel causes issues.

When running stress-test to make sure the fix is effective I uncovered
additional issues in get_common_dir_noenv. This function is used on each
worktree to build a worktree list.

Apparently it can happen that stat() claims there is a commondir file but when
trying to open the file it is missing.

Another even rarer issue is that the file might be zero size because another
process initializing a worktree opened the file but has not written is content

When any of this happnes git aborts failing to create a worktree because
unrelated worktree is not yet fully initialized.

I have tested that these patches fix the issue. However, I expect race against
removing/pruning worktrees is still possible.

For previous discussion see

Michal Suchanek (2):
  worktree: fix worktree add race.
  setup: don't fail if commondir reference is deleted.

 builtin/worktree.c | 12 +++++++-----
 setup.c            | 16 +++++++++++-----
 2 files changed, 18 insertions(+), 10 deletions(-)


             reply	other threads:[~2019-02-18 17:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 17:04 Michal Suchanek [this message]
2019-02-18 17:04 ` [PATCH 1/2] worktree: fix worktree add race Michal Suchanek
2019-02-18 17:04 ` [PATCH 2/2] setup: don't fail if commondir reference is deleted Michal Suchanek
2019-02-18 21:00   ` Eric Sunshine
2019-02-21 10:50   ` Duy Nguyen
2019-02-21 13:50     ` Michal Suchánek
2019-02-21 17:07       ` Phillip Wood
2019-02-21 17:12         ` Eric Sunshine
2019-02-21 17:27           ` Phillip Wood
2019-03-04 13:30             ` Michal Suchánek
2019-02-21 17:33           ` Michal Suchánek
2019-02-22  9:32         ` Duy Nguyen
2019-02-22 10:20           ` Phillip Wood
2019-02-22  9:26       ` Duy Nguyen
2019-02-20 16:16 ` [PATCH v3 1/2] worktree: fix worktree add race Michal Suchanek
2019-02-20 16:34   ` Eric Sunshine
2019-02-20 17:29     ` Michal Suchánek
2019-03-08  9:20   ` Duy Nguyen
2019-03-08  9:37     ` Eric Sunshine
2019-03-11  1:55     ` Junio C Hamano
2019-02-20 16:16 ` [PATCH v3 2/2] setup: don't fail if commondir reference is deleted Michal Suchanek
2019-02-20 16:55   ` Eric Sunshine
2019-02-20 17:16     ` Michal Suchánek
2019-02-20 18:35       ` Eric Sunshine
2019-02-21  9:27         ` Eric Sunshine
2019-02-21 11:13           ` Michal Suchánek
2019-02-21 11:19         ` Michal Suchánek

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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

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).