From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: mhagger@alum•mit.edu, git@vger•kernel.org
Subject: Re: [PATCH 3/3] refs.c: remove lock_fd from struct ref_lock
Date: Tue, 14 Apr 2015 16:12:03 -0700 [thread overview]
Message-ID: <xmqq8udu1f0c.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1429050308-9617-4-git-send-email-sbeller@google.com> (Stefan Beller's message of "Tue, 14 Apr 2015 15:25:08 -0700")
Stefan Beller <sbeller@google•com> writes:
> The 'lock_fd' is the same as 'lk->fd'. No need to store it twice so remove
> it. You may argue this introduces more coupling as we need to know more
> about the internals of the lock file mechanism, but this will be solved in
> a later patch.
>
> No functional changes intended.
It is somewhat strange to hear "in a later patch" in [PATCH 3/3] of
a 3-patch series ;-), but I think this makes sense. Whenever
we take a ref-lock, and we are going to actually write something
into the filesystem, we would go thru the lock_file API, so we can
depend on lk to have its own file descriptor field.
>
> Signed-off-by: Stefan Beller <sbeller@google•com>
> Signed-off-by: Junio C Hamano <gitster@pobox•com>
> ---
> refs.c | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/refs.c b/refs.c
> index 14e52ca..4066752 100644
> --- a/refs.c
> +++ b/refs.c
> @@ -11,7 +11,6 @@ struct ref_lock {
> char *orig_ref_name;
> struct lock_file *lk;
> unsigned char old_sha1[20];
> - int lock_fd;
> int force_write;
> };
>
> @@ -2259,7 +2258,6 @@ static struct ref_lock *lock_ref_sha1_basic(const char *refname,
> int attempts_remaining = 3;
>
> lock = xcalloc(1, sizeof(struct ref_lock));
> - lock->lock_fd = -1;
>
> if (mustexist)
> resolve_flags |= RESOLVE_REF_READING;
> @@ -2335,8 +2333,8 @@ static struct ref_lock *lock_ref_sha1_basic(const char *refname,
> goto error_return;
> }
>
> - lock->lock_fd = hold_lock_file_for_update(lock->lk, ref_file, lflags);
> - if (lock->lock_fd < 0) {
> + if (hold_lock_file_for_update(lock->lk, ref_file, lflags) < 0) {
> + last_errno = errno;
> if (errno == ENOENT && --attempts_remaining > 0)
> /*
> * Maybe somebody just deleted one of the
> @@ -2904,7 +2902,6 @@ static int close_ref(struct ref_lock *lock)
> {
> if (close_lock_file(lock->lk))
> return -1;
> - lock->lock_fd = -1;
> return 0;
> }
>
> @@ -2912,7 +2909,6 @@ static int commit_ref(struct ref_lock *lock)
> {
> if (commit_lock_file(lock->lk))
> return -1;
> - lock->lock_fd = -1;
> return 0;
> }
>
> @@ -3090,8 +3086,8 @@ static int write_ref_sha1(struct ref_lock *lock,
> errno = EINVAL;
> return -1;
> }
> - if (write_in_full(lock->lock_fd, sha1_to_hex(sha1), 40) != 40 ||
> - write_in_full(lock->lock_fd, &term, 1) != 1 ||
> + if (write_in_full(lock->lk->fd, sha1_to_hex(sha1), 40) != 40 ||
> + write_in_full(lock->lk->fd, &term, 1) != 1 ||
> close_ref(lock) < 0) {
> int save_errno = errno;
> error("Couldn't write %s", lock->lk->filename.buf);
> @@ -4047,9 +4043,9 @@ int reflog_expire(const char *refname, const unsigned char *sha1,
> status |= error("couldn't write %s: %s", log_file,
> strerror(errno));
> } else if ((flags & EXPIRE_REFLOGS_UPDATE_REF) &&
> - (write_in_full(lock->lock_fd,
> + (write_in_full(lock->lk->fd,
> sha1_to_hex(cb.last_kept_sha1), 40) != 40 ||
> - write_str_in_full(lock->lock_fd, "\n") != 1 ||
> + write_str_in_full(lock->lk->fd, "\n") != 1 ||
> close_ref(lock) < 0)) {
> status |= error("couldn't write %s",
> lock->lk->filename.buf);
next prev parent reply other threads:[~2015-04-14 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 22:25 [PATCH 0/3] Large transactions in git Stefan Beller
2015-04-14 22:25 ` [PATCH 1/3] update-ref: test handling large transactions properly Stefan Beller
2015-04-14 22:25 ` [PATCH 2/3] t7004: rename ULIMIT test prerequisite to ULIMIT_STACK_SIZE Stefan Beller
2015-04-14 22:25 ` [PATCH 3/3] refs.c: remove lock_fd from struct ref_lock Stefan Beller
2015-04-14 23:12 ` Junio C Hamano [this message]
2015-04-15 8:49 ` Michael Haggerty
2015-04-15 18:35 ` Junio C Hamano
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=xmqq8udu1f0c.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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