From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, gitster@pobox.com, mhagger@alum.mit.edu
Cc: Ronnie Sahlberg <sahlberg@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Stefan Beller <sbeller@google.com>
Subject: [PATCH v4 02/16] refs.c: return error instead of dying when locking fails during transaction
Date: Mon, 17 Nov 2014 17:44:43 -0800 [thread overview]
Message-ID: <1416275097-3616-3-git-send-email-sbeller@google.com> (raw)
In-Reply-To: <1416275097-3616-1-git-send-email-sbeller@google.com>
From: Ronnie Sahlberg <sahlberg@google.com>
Change lock_ref_sha1_basic to return an error instead of dying when
we fail to lock a file during a transaction.
This function is only called from transaction_commit() and it knows how
to handle these failures.
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
---
refs.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/refs.c b/refs.c
index f30512f..78eb46f 100644
--- a/refs.c
+++ b/refs.c
@@ -2340,6 +2340,7 @@ static struct ref_lock *lock_ref_sha1_basic(const char *refname,
lock->lock_fd = hold_lock_file_for_update(lock->lk, ref_file, lflags);
if (lock->lock_fd < 0) {
+ last_errno = errno;
if (errno == ENOENT && --attempts_remaining > 0)
/*
* Maybe somebody just deleted one of the
@@ -2347,8 +2348,13 @@ static struct ref_lock *lock_ref_sha1_basic(const char *refname,
* again:
*/
goto retry;
- else
- unable_to_lock_die(ref_file, errno);
+ else {
+ struct strbuf err = STRBUF_INIT;
+ unable_to_lock_message(ref_file, errno, &err);
+ error("%s", err.buf);
+ strbuf_reset(&err);
+ goto error_return;
+ }
}
return old_sha1 ? verify_lock(lock, old_sha1, mustexist) : lock;
--
2.2.0.rc2.5.gf7b9fb2
next prev parent reply other threads:[~2014-11-18 1:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 1:44 [PATCH v4 00/16] ref-transaction-rename Stefan Beller
2014-11-18 1:44 ` [PATCH v4 01/16] refs.c: allow passing raw git_committer_info as email to _update_reflog Stefan Beller
2014-11-18 1:44 ` Stefan Beller [this message]
2014-11-18 1:44 ` [PATCH v4 03/16] refs.c: use packed refs when deleting refs during a transaction Stefan Beller
2014-11-18 1:44 ` [PATCH v4 04/16] refs.c: use a stringlist for repack_without_refs Stefan Beller
2014-11-18 1:44 ` [PATCH v4 05/16] refs.c: add transaction support for renaming a reflog Stefan Beller
2014-11-18 1:44 ` [PATCH v4 06/16] refs.c: update rename_ref to use a transaction Stefan Beller
2014-11-18 1:44 ` [PATCH v4 07/16] refs.c: rollback the lockfile before we die() in repack_without_refs Stefan Beller
2014-11-18 1:44 ` [PATCH v4 08/16] refs.c: move reflog updates into its own function Stefan Beller
2014-11-18 1:44 ` [PATCH v4 09/16] refs.c: write updates to packed refs when a transaction has more than one ref Stefan Beller
2014-11-18 1:44 ` [PATCH v4 10/16] remote.c: use a transaction for deleting refs Stefan Beller
2014-11-18 1:44 ` [PATCH v4 11/16] refs.c: make repack_without_refs static Stefan Beller
2014-11-18 1:44 ` [PATCH v4 12/16] refs.c: make the *_packed_refs functions static Stefan Beller
2014-11-18 1:44 ` [PATCH v4 13/16] refs.c: replace the onerr argument in update_ref with a strbuf err Stefan Beller
2014-11-18 1:44 ` [PATCH v4 14/16] refs.c: make add_packed_ref return an error instead of calling die Stefan Beller
2014-11-18 1:44 ` [PATCH v4 15/16] refs.c: make lock_packed_refs take an err argument Stefan Beller
2014-11-18 1:44 ` [PATCH v4 16/16] refs.c: add an err argument to pack_refs Stefan Beller
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=1416275097-3616-3-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=sahlberg@google.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;
as well as URLs for NNTP newsgroup(s).