git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <sbeller@google.com>
To: sahlberg@google.com, jrnieder@gmail.com, gitster@pobox.com,
	git@vger.kernel.org
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCH] refs.c: add a function to append a reflog entry to a fd
Date: Wed, 19 Nov 2014 16:42:22 -0800	[thread overview]
Message-ID: <1416444142-28042-1-git-send-email-sbeller@google.com> (raw)

From: Ronnie Sahlberg <sahlberg@google.com>

Break out the code to create the string and writing it to the file
descriptor from log_ref_write and add it into a dedicated function
log_ref_write_fd. For now this is only used from log_ref_write,
but later on we will call this function from reflog transactions too,
which means that we will end up with only a single place,
where we write a reflog entry to a file instead of the current two
places (log_ref_write and builtin/reflog.c).

[sb: replaced sprintf by snprintf for security reasons, 
     which was there in the beginning (6de08ae688b9f2, 2006-06-17, 
     Log ref updates to logs/refs/<ref>), but got lost in (8ac65937d032ad, 
     2007-01-26, Make sure we do not write bogus reflog entries.)
]

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 | 48 ++++++++++++++++++++++++++++++------------------
 1 file changed, 30 insertions(+), 18 deletions(-)

This is also part of the ref-transaction-reflog series, but is 
sufficiently independant, that I'd argue it's a general code hygiene thing,
we can use in any case.

Applies on master.

Compared to the last send of this patch[1], there was one change in the print
function. Replaced sprintf by snprintf for security reasons. 

[1] part of the ref-transaction-reflog series 
    http://permalink.gmane.org/gmane.comp.version-control.git/259714
 

diff --git a/refs.c b/refs.c
index 5ff457e..f9b42e5 100644
--- a/refs.c
+++ b/refs.c
@@ -2990,15 +2990,37 @@ int log_ref_setup(const char *refname, char *logfile, int bufsize)
 	return 0;
 }
 
+static int log_ref_write_fd(int fd, const unsigned char *old_sha1,
+			    const unsigned char *new_sha1,
+			    const char *committer, const char *msg)
+{
+	int msglen, written;
+	unsigned maxlen, len;
+	char *logrec;
+
+	msglen = msg ? strlen(msg) : 0;
+	maxlen = strlen(committer) + msglen + 100;
+	logrec = xmalloc(maxlen);
+	len = snprintf(logrec, maxlen, "%s %s %s\n",
+		       sha1_to_hex(old_sha1),
+		       sha1_to_hex(new_sha1),
+		       committer);
+	if (msglen)
+		len += copy_msg(logrec + len - 1, msg) - 1;
+
+	written = len <= maxlen ? write_in_full(fd, logrec, len) : -1;
+	free(logrec);
+	if (written != len)
+		return -1;
+
+	return 0;
+}
+
 static int log_ref_write(const char *refname, const unsigned char *old_sha1,
 			 const unsigned char *new_sha1, const char *msg)
 {
-	int logfd, result, written, oflags = O_APPEND | O_WRONLY;
-	unsigned maxlen, len;
-	int msglen;
+	int logfd, result, oflags = O_APPEND | O_WRONLY;
 	char log_file[PATH_MAX];
-	char *logrec;
-	const char *committer;
 
 	if (log_all_ref_updates < 0)
 		log_all_ref_updates = !is_bare_repository();
@@ -3010,19 +3032,9 @@ static int log_ref_write(const char *refname, const unsigned char *old_sha1,
 	logfd = open(log_file, oflags);
 	if (logfd < 0)
 		return 0;
-	msglen = msg ? strlen(msg) : 0;
-	committer = git_committer_info(0);
-	maxlen = strlen(committer) + msglen + 100;
-	logrec = xmalloc(maxlen);
-	len = sprintf(logrec, "%s %s %s\n",
-		      sha1_to_hex(old_sha1),
-		      sha1_to_hex(new_sha1),
-		      committer);
-	if (msglen)
-		len += copy_msg(logrec + len - 1, msg) - 1;
-	written = len <= maxlen ? write_in_full(logfd, logrec, len) : -1;
-	free(logrec);
-	if (written != len) {
+	result = log_ref_write_fd(logfd, old_sha1, new_sha1,
+				  git_committer_info(0), msg);
+	if (result) {
 		int save_errno = errno;
 		close(logfd);
 		error("Unable to append to %s", log_file);
-- 
2.2.0.rc2.13.g0786cdb

             reply	other threads:[~2014-11-20  0:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  0:42 Stefan Beller [this message]
2014-11-20  1:22 ` [PATCH] refs.c: add a function to append a reflog entry to a fd Junio C Hamano
2014-11-20  1:34   ` Junio C Hamano
2014-11-20  2:05     ` Stefan Beller
2014-11-20  2:36       ` Jonathan Nieder
2014-11-20 16:57         ` Junio C Hamano
2014-11-20 18:37         ` [PATCH v3] " Stefan Beller
2014-11-20 21:20           ` Jonathan Nieder
2014-11-20 21:24             ` Stefan Beller
2014-11-20 21:31               ` Jonathan Nieder
2014-11-20 21:42           ` Junio C Hamano
2014-11-20 21:58             ` Stefan Beller
2014-11-20 22:05               ` Jonathan Nieder
2014-11-20 22:11                 ` Junio C Hamano
2014-11-20 21:59             ` [PATCH v4] " Stefan Beller
2014-11-20 22:11               ` Jonathan Nieder
2014-11-20 22:29                 ` Junio C Hamano
2014-11-20  1:42 ` [PATCH] " Jonathan Nieder

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=1416444142-28042-1-git-send-email-sbeller@google.com \
    --to=sbeller@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --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).