From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: mhagger@alum.mit.edu, Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH v5 16/30] branch.c: use ref transaction for all ref updates
Date: Tue, 29 Apr 2014 15:19:01 -0700 [thread overview]
Message-ID: <1398809955-32008-17-git-send-email-sahlberg@google.com> (raw)
In-Reply-To: <1398809955-32008-1-git-send-email-sahlberg@google.com>
Change create_branch to use a ref transaction when creating the new branch.
ref_transaction_create will check that the ref does not already exist and fail
otherwise meaning that we no longer need to keep a lock on the ref during the
setup_tracking. This simplifies the code since we can now do the transaction
in one single step.
If the forcing flag is false then use ref_transaction_create since this will
fail if the ref already exist. Otherwise use ref_transaction_update.
This also fixes a race condition in the old code where two concurrent
create_branch could race since the lock_any_ref_for_update/write_ref_sha1
did not protect against the ref already existsing. I.e. one thread could end up
overwriting a branch even if the forcing flag is false.
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
---
branch.c | 30 ++++++++++++++++--------------
1 file changed, 16 insertions(+), 14 deletions(-)
diff --git a/branch.c b/branch.c
index 660097b..2aa5c82 100644
--- a/branch.c
+++ b/branch.c
@@ -226,7 +226,6 @@ void create_branch(const char *head,
int force, int reflog, int clobber_head,
int quiet, enum branch_track track)
{
- struct ref_lock *lock = NULL;
struct commit *commit;
unsigned char sha1[20];
char *real_ref, msg[PATH_MAX + 20];
@@ -285,15 +284,6 @@ void create_branch(const char *head,
die(_("Not a valid branch point: '%s'."), start_name);
hashcpy(sha1, commit->object.sha1);
- if (!dont_change_ref) {
- lock = lock_any_ref_for_update(ref.buf, NULL, 0, NULL);
- if (!lock)
- die_errno(_("Failed to lock ref for update"));
- }
-
- if (reflog)
- log_all_ref_updates = 1;
-
if (forcing)
snprintf(msg, sizeof msg, "branch: Reset to %s",
start_name);
@@ -301,13 +291,25 @@ void create_branch(const char *head,
snprintf(msg, sizeof msg, "branch: Created from %s",
start_name);
+ if (reflog)
+ log_all_ref_updates = 1;
+
+ if (!dont_change_ref) {
+ struct ref_transaction *transaction;
+ struct strbuf err = STRBUF_INIT;
+
+ transaction = ref_transaction_begin();
+ if (!transaction ||
+ ref_transaction_update(transaction, ref.buf, sha1,
+ null_sha1, 0, !forcing) ||
+ ref_transaction_commit(transaction, msg, &err))
+ die_errno(_("%s: failed to write ref: %s"),
+ ref.buf, err.buf);
+ }
+
if (real_ref && track)
setup_tracking(ref.buf + 11, real_ref, track, quiet);
- if (!dont_change_ref)
- if (write_ref_sha1(lock, sha1, msg) < 0)
- die_errno(_("Failed to write ref"));
-
strbuf_release(&ref);
free(real_ref);
}
--
1.9.1.532.gf8485a6
next prev parent reply other threads:[~2014-04-29 22:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 22:18 [PATCH v5 00/30] Use ref transactions for all ref updates Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 01/30] refs.c: constify the sha arguments for ref_transaction_create|delete|update Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 02/30] refs.c: allow passing NULL to ref_transaction_free Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 03/30] refs.c: add a strbuf argument to ref_transaction_commit for error logging Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 04/30] refs.c: make ref_update_reject_duplicates take a strbuf argument for errors Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 05/30] update-ref.c: log transaction error from the update_ref Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 06/30] refs.c: make update_ref_write update a strbuf on failure Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 07/30] refs.c: remove the onerr argument to ref_transaction_commit Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 08/30] refs.c: change ref_transaction_update() to do error checking and return status Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 09/30] refs.c: change ref_transaction_create " Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 10/30] refs.c: ref_transaction_delete to check for error " Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 11/30] tag.c: use ref transactions when doing updates Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 12/30] replace.c: use the ref transaction functions for updates Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 13/30] commit.c: use ref transactions " Ronnie Sahlberg
2014-04-29 22:18 ` [PATCH v5 14/30] sequencer.c: use ref transactions for all ref updates Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 15/30] fast-import.c: change update_branch to use ref transactions Ronnie Sahlberg
2014-04-29 22:19 ` Ronnie Sahlberg [this message]
2014-04-29 22:19 ` [PATCH v5 17/30] refs.c: change update_ref to use a transaction Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 18/30] refs.c: free the transaction before returning when number of updates is 0 Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 19/30] refs.c: ref_transaction_commit should not free the transaction Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 20/30] fetch.c: clear errno before calling functions that might set it Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 21/30] fetch.c: change s_update_ref to use a ref transaction Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 22/30] fetch.c: use a single ref transaction for all ref updates Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 23/30] receive-pack.c: use a reference transaction for updating the refs Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 24/30] fast-import.c: use a ref transaction when dumping tags Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 25/30] walker.c: use ref transaction for ref updates Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 26/30] refs.c: make write_ref_sha1 static Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 27/30] refs.c: make lock_ref_sha1 static Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 28/30] refs.c: add transaction.status and track OPEN/CLOSED/ERROR Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 29/30] refs.c: remove the update_ref_lock function Ronnie Sahlberg
2014-04-29 22:19 ` [PATCH v5 30/30] refs.c: remove the update_ref_write function Ronnie Sahlberg
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=1398809955-32008-17-git-send-email-sahlberg@google.com \
--to=sahlberg@google.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).