git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Don't coredump on bad refs in update-server-info.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jan 31, 2007, 07:24 UTC
Message-ID
<20070131072444.GA28804@spearce.org>

Apparently if we are unable to parse an object update-server-info coredumps, as it doesn't bother to check the return value of its call to parse_object.

Instead of coredumping, skip the ref.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
 I don't know how often folks might run into this.  I intentionally
 broke pack reading in one of my topics and discovered that
 update-server-info crashed with a segfault when the pack access code
 was unable to decompress the object behind the ref.  That's less
 than optimal.
 server-info.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/server-info.c b/server-info.c
index 6cd38be..f9be5a7 100644
--- a/server-info.c
+++ b/server-info.c
@@ -10,6 +10,8 @@ static FILE *info_ref_fp;
 static int add_info_ref(const char *path, const unsigned char *sha1, int flag, void *cb_data)
 {
 	struct object *o = parse_object(sha1);
+	if (!o)
+		return -1;
 
 	fprintf(info_ref_fp, "%s	%s\n", sha1_to_hex(sha1), path);
 	if (o->type == OBJ_TAG) {
-- 
1.5.0.rc2.81.g73a2
Next: Jakub Narebski
Message 1 of 2 in “Don't coredump on bad refs in update-server-info.”
  1. Don't coredump on bad refs in update-server-info.Shawn O. Pearce, Jan 31, 2007
  2. Jakub NarebskiJan 31, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.