From: Jun Wu <quark.zju@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, ps@pks.im, Jun Wu <quark@meta.com>
Subject: [PATCH v2 4/4] reset: fix write race
Date: Sat, 17 Oct 2026 00:32:31 -0700 [thread overview]
Message-ID: <20261017073231.3357477-5-quark.zju@gmail.com> (raw)
In-Reply-To: <20261017073231.3357477-1-quark.zju@gmail.com>
From: Jun Wu <quark@meta.com>
Similar to the previous commit "commit: fix write race", fix a similar race in
"reset" (except for --soft, which does not lock/write the index) by changing
"read -> lock -> write" to "lock -> read -> write", so "reset" now qualifies
the new user-friendly "waiting for index lock" behavior.
Unlike "commit", "reset" uses repo_read_index(), not repo_read_index_preload(),
so it won't add significant work (e.g. lstat() working tree) while holding the
index lock.
I chose to not add a test to t0032-index-lock-timeout.sh, since every waiting
test case there (undesirably) takes 1 second to run, there are already
representative test cases, and the change looks straightforward.
Signed-off-by: Jun Wu <quark@meta.com>
---
builtin/reset.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/builtin/reset.c b/builtin/reset.c
index 78e69bd84b..0e1aa76aaa 100644
--- a/builtin/reset.c
+++ b/builtin/reset.c
@@ -346,6 +346,7 @@ int cmd_reset(int argc,
struct object_id oid;
struct pathspec pathspec;
int intent_to_add = 0;
+ struct lock_file lock = LOCK_INIT;
struct interactive_options interactive_opts = INTERACTIVE_OPTIONS_INIT;
const struct option options[] = {
OPT__QUIET(&quiet, N_("be quiet, only report errors")),
@@ -477,6 +478,9 @@ int cmd_reset(int argc,
if (intent_to_add && reset_type != MIXED)
die(_("the option '%s' requires '%s'"), "-N", "--mixed");
+ if (reset_type != SOFT)
+ repo_hold_locked_index(the_repository, &lock,
+ LOCK_DIE_ON_ERROR);
if (repo_read_index(the_repository) < 0)
die(_("index file corrupt"));
@@ -487,9 +491,6 @@ int cmd_reset(int argc,
die_if_unmerged_cache(reset_type);
if (reset_type != SOFT) {
- struct lock_file lock = LOCK_INIT;
- repo_hold_locked_index(the_repository, &lock,
- LOCK_DIE_ON_ERROR);
if (reset_type == MIXED) {
int flags = quiet ? REFRESH_QUIET : REFRESH_IN_PORCELAIN;
if (read_from_tree(&pathspec, &oid, intent_to_add)) {
--
2.56.0
prev parent reply other threads:[~2026-10-17 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 17:23 [PATCH 0/2] Add a way to wait for index lock Jun Wu
2026-10-13 17:23 ` [PATCH 1/2] repository: add core.indexLockTimeout Jun Wu
2026-10-13 21:40 ` D. Ben Knoble
2026-10-14 2:38 ` Jun Wu
2026-10-14 16:29 ` D. Ben Knoble
2026-10-13 22:05 ` Junio C Hamano
2026-10-14 22:12 ` Jun Wu
2026-10-13 17:23 ` [PATCH 2/2] commit: lock index before reading Jun Wu
2026-10-14 10:04 ` Jeff King
2026-10-15 0:19 ` Jun Wu
2026-10-13 22:05 ` [PATCH 0/2] Add a way to wait for index lock Junio C Hamano
2026-10-14 22:12 ` Jun Wu
2026-10-14 10:14 ` Jeff King
2026-10-17 7:32 ` [PATCH v2 0/4] Wait for the index lock instead of failing Jun Wu
2026-10-17 7:32 ` [PATCH v2 1/4] repository: add repo_try_hold_locked_index() Jun Wu
2026-10-17 7:32 ` [PATCH v2 2/4] repository: add core.indexLockTimeout Jun Wu
2026-10-17 7:32 ` [PATCH v2 3/4] commit: fix write race Jun Wu
2026-10-17 7:32 ` Jun Wu [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261017073231.3357477-5-quark.zju@gmail.com \
--to=quark.zju@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=quark@meta.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox