From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH v17 21/48] refs.c: change ref_transaction_create to do error checking and return status
Date: Mon, 16 Jun 2014 11:03:52 -0700 [thread overview]
Message-ID: <1402941859-29354-22-git-send-email-sahlberg@google.com> (raw)
In-Reply-To: <1402941859-29354-1-git-send-email-sahlberg@google.com>
Do basic error checking in ref_transaction_create() and make it return
non-zero on error. Update all callers to check the result of
ref_transaction_create(). There are currently no conditions in _create that
will return error but there will be in the future. Add an err argument that
will be updated on failure.
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
---
builtin/update-ref.c | 4 +++-
refs.c | 18 +++++++++++------
refs.h | 55 +++++++++++++++++++++++++++++++++++++++++++++-------
3 files changed, 63 insertions(+), 14 deletions(-)
diff --git a/builtin/update-ref.c b/builtin/update-ref.c
index 3067b11..41121fa 100644
--- a/builtin/update-ref.c
+++ b/builtin/update-ref.c
@@ -226,7 +226,9 @@ static const char *parse_cmd_create(struct strbuf *input, const char *next)
if (*next != line_termination)
die("create %s: extra input: %s", refname, next);
- ref_transaction_create(transaction, refname, new_sha1, update_flags);
+ if (ref_transaction_create(transaction, refname, new_sha1,
+ update_flags, &err))
+ die("%s", err.buf);
update_flags = 0;
free(refname);
diff --git a/refs.c b/refs.c
index 9c02687..3dab75c 100644
--- a/refs.c
+++ b/refs.c
@@ -3446,18 +3446,24 @@ int ref_transaction_update(struct ref_transaction *transaction,
return 0;
}
-void ref_transaction_create(struct ref_transaction *transaction,
- const char *refname,
- const unsigned char *new_sha1,
- int flags)
+int ref_transaction_create(struct ref_transaction *transaction,
+ const char *refname,
+ const unsigned char *new_sha1,
+ int flags,
+ struct strbuf *err)
{
- struct ref_update *update = add_update(transaction, refname);
+ struct ref_update *update;
+
+ if (!new_sha1 || is_null_sha1(new_sha1))
+ die("BUG: create ref with null new_sha1");
+
+ update = add_update(transaction, refname);
- assert(!is_null_sha1(new_sha1));
hashcpy(update->new_sha1, new_sha1);
hashclr(update->old_sha1);
update->flags = flags;
update->have_old = 1;
+ return 0;
}
void ref_transaction_delete(struct ref_transaction *transaction,
diff --git a/refs.h b/refs.h
index f7a5e42..27c470c 100644
--- a/refs.h
+++ b/refs.h
@@ -10,6 +10,45 @@ struct ref_lock {
int force_write;
};
+/*
+ * A ref_transaction represents a collection of ref updates
+ * that should succeed or fail together.
+ *
+ * Calling sequence
+ * ----------------
+ * - Allocate and initialize a `struct ref_transaction` by calling
+ * `ref_transaction_begin()`.
+ *
+ * - List intended ref updates by calling functions like
+ * `ref_transaction_update()` and `ref_transaction_create()`.
+ *
+ * - Call `ref_transaction_commit()` to execute the transaction.
+ * If this succeeds, the ref updates will have taken place and
+ * the transaction cannot be rolled back.
+ *
+ * - At any time call `ref_transaction_free()` to discard the
+ * transaction and free associated resources. In particular,
+ * this rolls back the transaction if it has not been
+ * successfully committed.
+ *
+ * Error handling
+ * --------------
+ *
+ * On error, transaction functions append a message about what
+ * went wrong to the 'err' argument. The message mentions what
+ * ref was being updated (if any) when the error occurred so it
+ * can be passed to 'die' or 'error' as-is.
+ *
+ * The message is appended to err without first clearing err.
+ * This allows the caller to prepare preamble text to the generated
+ * error message:
+ *
+ * strbuf_addf(&err, "Error while doing foo-bar: ");
+ * if (ref_transaction_update(..., &err)) {
+ * ret = error("%s", err.buf);
+ * goto cleanup;
+ * }
+ */
struct ref_transaction;
/*
@@ -244,7 +283,7 @@ struct ref_transaction *ref_transaction_begin(void);
* it must not have existed beforehand.
* Function returns 0 on success and non-zero on failure. A failure to update
* means that the transaction as a whole has failed and will need to be
- * rolled back. On failure the err buffer will be updated.
+ * rolled back.
*/
int ref_transaction_update(struct ref_transaction *transaction,
const char *refname,
@@ -258,11 +297,15 @@ int ref_transaction_update(struct ref_transaction *transaction,
* that the reference should have after the update; it must not be the
* null SHA-1. It is verified that the reference does not exist
* already.
+ * Function returns 0 on success and non-zero on failure. A failure to create
+ * means that the transaction as a whole has failed and will need to be
+ * rolled back.
*/
-void ref_transaction_create(struct ref_transaction *transaction,
- const char *refname,
- const unsigned char *new_sha1,
- int flags);
+int ref_transaction_create(struct ref_transaction *transaction,
+ const char *refname,
+ const unsigned char *new_sha1,
+ int flags,
+ struct strbuf *err);
/*
* Add a reference deletion to transaction. If have_old is true, then
@@ -278,8 +321,6 @@ void ref_transaction_delete(struct ref_transaction *transaction,
* Commit all of the changes that have been queued in transaction, as
* atomically as possible. Return a nonzero value if there is a
* problem.
- * If err is non-NULL we will add an error string to it to explain why
- * the transaction failed. The string does not end in newline.
*/
int ref_transaction_commit(struct ref_transaction *transaction,
const char *msg, struct strbuf *err);
--
2.0.0.282.g3799eda.dirty
next prev parent reply other threads:[~2014-06-16 18:08 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 18:03 [PATCH v17 00/48] Use ref transactions Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 01/48] refs.c: remove ref_transaction_rollback Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 02/48] refs.c: ref_transaction_commit should not free the transaction Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 03/48] refs.c: constify the sha arguments for ref_transaction_create|delete|update Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 04/48] refs.c: allow passing NULL to ref_transaction_free Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 05/48] refs.c: add a strbuf argument to ref_transaction_commit for error logging Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 06/48] lockfile.c: add a new public function unable_to_lock_message Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 07/48] lockfile.c: make lock_file return a meaningful errno on failurei Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 08/48] refs.c: add an err argument to repack_without_refs Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 09/48] refs.c: make sure log_ref_setup returns a meaningful errno Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 10/48] refs.c: verify_lock should set errno to something meaningful Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 11/48] refs.c: make remove_empty_directories alwasy set errno to something sane Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 12/48] refs.c: commit_packed_refs to return a meaningful errno on failure Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 13/48] refs.c: make resolve_ref_unsafe set errno to something meaningful on error Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 14/48] refs.c: log_ref_write should try to return meaningful errno Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 15/48] refs.c: make ref_update_reject_duplicates take a strbuf argument for errors Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 16/48] refs.c: add an err argument to delete_ref_loose Ronnie Sahlberg
2014-06-17 0:22 ` Junio C Hamano
2014-06-17 14:34 ` Ronnie Sahlberg
2014-06-17 15:55 ` Ronnie Sahlberg
2014-06-17 17:23 ` Junio C Hamano
2014-06-16 18:03 ` [PATCH v17 17/48] refs.c: make update_ref_write update a strbuf on failure Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 18/48] update-ref: use err argument to get error from ref_transaction_commit Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 19/48] refs.c: remove the onerr argument to ref_transaction_commit Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 20/48] refs.c: change ref_transaction_update() to do error checking and return status Ronnie Sahlberg
2014-06-16 18:03 ` Ronnie Sahlberg [this message]
2014-06-16 18:03 ` [PATCH v17 22/48] refs.c: update ref_transaction_delete to check for error " Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 23/48] refs.c: make ref_transaction_begin take an err argument Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 24/48] refs.c: add transaction.status and track OPEN/CLOSED/ERROR Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 25/48] tag.c: use ref transactions when doing updates Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 26/48] replace.c: use the ref transaction functions for updates Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 27/48] commit.c: use ref transactions " Ronnie Sahlberg
2014-06-16 18:03 ` [PATCH v17 28/48] sequencer.c: use ref transactions for all ref updates Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 29/48] fast-import.c: change update_branch to use ref transactions Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 30/48] branch.c: use ref transaction for all ref updates Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 31/48] refs.c: change update_ref to use a transaction Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 32/48] receive-pack.c: use a reference transaction for updating the refs Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 33/48] fast-import.c: use a ref transaction when dumping tags Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 34/48] walker.c: use ref transaction for ref updates Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 35/48] refs.c: make lock_ref_sha1 static Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 36/48] refs.c: remove the update_ref_lock function Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 37/48] refs.c: remove the update_ref_write function Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 38/48] refs.c: remove lock_ref_sha1 Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 39/48] refs.c: make prune_ref use a transaction to delete the ref Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 40/48] refs.c: make delete_ref use a transaction Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 41/48] refs.c: pass the ref log message to _create/delete/update instead of _commit Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 42/48] refs.c: pass NULL as *flags to read_ref_full Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 43/48] refs.c: move the check for valid refname to lock_ref_sha1_basic Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 44/48] refs.c: call lock_ref_sha1_basic directly from commit Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 45/48] refs.c: pass a skip list to name_conflict_fn Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 46/48] refs.c: propagate any errno==ENOTDIR from _commit back to the callers Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 47/48] fetch.c: change s_update_ref to use a ref transaction Ronnie Sahlberg
2014-06-16 18:04 ` [PATCH v17 48/48] refs.c: make write_ref_sha1 static 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
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=1402941859-29354-22-git-send-email-sahlberg@google.com \
--to=sahlberg@google.com \
--cc=git@vger.kernel.org \
/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).