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

[PATCH 3/3] Prevent send-pack from segfaulting when a branch doesn't match

From
Shawn O. Pearce <spearce@spearce.org>
Date
Sep 25, 2007, 04:13 UTC
Message-ID
<20070925041325.GC11363@spearce.org>

If `git push url foo` can't find a local branch named foo we can't match it to any remote branch as the local branch is NULL and its name is probably at position 0x34 in memory. On most systems that isn't a valid address for git-send-pack's virtual address space and we segfault.

If we can't find a source match and we have no destination we need to abort the match function early before we try to match the destination against the remote.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
 remote.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/remote.c b/remote.c
index 2166a2b..e7d735b 100644
--- a/remote.c
+++ b/remote.c
@@ -610,8 +610,11 @@ static int match_explicit(struct ref *src, struct ref *dst,
 	if (!matched_src)
 		errs = 1;
 
-	if (!dst_value)
+	if (!dst_value) {
+		if (!matched_src)
+			return errs;
 		dst_value = matched_src->name;
+	}
 
 	switch (count_refspec_match(dst_value, dst, &matched_dst)) {
 	case 1:
-- 
1.5.3.2.124.g2456-dirty
Message 1 of 1 in “Prevent send-pack from segfaulting when a branch doesn't match”
  1. 3/3 Prevent send-pack from segfaulting when a branch doesn't matchShawn O. Pearce, Sep 25, 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.