From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: [PATCH 2/8] Add a lockfile function to append to a file
Date: Thu, 17 Apr 2008 20:02:31 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0804171950140.19665@iabervon.org> (raw)
This takes care of copying the original contents into the replacement
file after the lock is held, so that concurrent additions can't miss
each other's changes.
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
---
How about this? Also doesn't leak a fd and catches trying to append to a
file you can't read. Should I worry about mmap failing after the open?
cache.h | 1 +
lockfile.c | 23 +++++++++++++++++++++++
2 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/cache.h b/cache.h
index 50b28fa..8d066bf 100644
--- a/cache.h
+++ b/cache.h
@@ -391,6 +391,7 @@ struct lock_file {
char filename[PATH_MAX];
};
extern int hold_lock_file_for_update(struct lock_file *, const char *path, int);
+extern int hold_lock_file_for_append(struct lock_file *, const char *path, int);
extern int commit_lock_file(struct lock_file *);
extern int hold_locked_index(struct lock_file *, int);
diff --git a/lockfile.c b/lockfile.c
index 663f18f..f1b5416 100644
--- a/lockfile.c
+++ b/lockfile.c
@@ -160,6 +160,29 @@ int hold_lock_file_for_update(struct lock_file *lk, const char *path, int die_on
return fd;
}
+int hold_lock_file_for_append(struct lock_file *lk, const char *path, int die_on_error)
+{
+ int fd = lock_file(lk, path);
+ struct stat st;
+ if (fd < 0) {
+ if (die_on_error)
+ die("unable to create '%s.lock': %s",
+ path, strerror(errno));
+ } else if (!stat(path, &st)) {
+ int orig_fd = open(path, O_RDONLY);
+ size_t mmap_size = xsize_t(st.st_size);
+ void *mmap;
+ if (orig_fd < 0)
+ die("unable to read %s to append to it", path);
+ mmap = xmmap(NULL, mmap_size, PROT_READ, MAP_PRIVATE,
+ orig_fd, 0);
+ write_or_die(fd, mmap, mmap_size);
+ munmap(mmap, mmap_size);
+ close(orig_fd);
+ }
+ return fd;
+}
+
int close_lock_file(struct lock_file *lk)
{
int fd = lk->fd;
--
1.5.4.3.610.gea6cd
next reply other threads:[~2008-04-18 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 0:02 Daniel Barkalow [this message]
2008-04-20 4:59 ` [PATCH 2/8] Add a lockfile function to append to a file Junio C Hamano
2008-04-20 16:14 ` Johannes Schindelin
2008-04-20 19:43 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2008-04-17 23:32 Daniel Barkalow
2008-04-17 23:41 ` Junio C Hamano
2008-04-17 23:51 ` 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
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=alpine.LNX.1.00.0804171950140.19665@iabervon.org \
--to=barkalow@iabervon.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).