From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Segfault in "git remote show <remote-name>"
Date: Mon, 25 May 2009 18:10:12 +0200 [thread overview]
Message-ID: <40aa078e0905250910v268faa66p29a0183db26cb0df@mail.gmail.com> (raw)
I've been messing around a bit, trying to set up a gitosis repo to
mirror one of my projects. Now, I added the remote to my project, but
when running "git remote show <remote-name>", I'm getting a segfault
in builtin-remote.c at line 303 ("while (ref->next)"), because ref
itself is NULL. The offending function itself (get_push_ref_states) is
called with NULL as the remote_refs parameters, leading to a
NULL-pointer dereferencing.
Here's the backtrace from the crash:
(gdb) bt
#0 get_push_ref_states (remote_refs=0x0, states=0x27fcdc)
at builtin-remote.c:303
#1 0x00444301 in get_remote_ref_states (name=0x342bcb "origin_new",
states=0x27fcdc, query=7) at builtin-remote.c:803
#2 0x004449ae in show (argc=1, argv=0x342d0c) at builtin-remote.c:1004
#3 0x0044593b in cmd_remote (argc=2, argv=0x342d0c, prefix=0x0)
at builtin-remote.c:1323
#4 0x00401bc7 in run_builtin (p=0x4e8338, argc=3, argv=0x342d0c) at git.c:247
#5 0x00401dab in handle_internal_command (argc=3, argv=0x342d0c) at git.c:392
#6 0x00401ea7 in run_argv (argcp=0x27ff30, argv=0x27ff34) at git.c:438
#7 0x00402036 in mingw_main (argc=3, argv=0x342d0c) at git.c:509
#8 0x00401f12 in main (argc=4, argv=0x342d08) at git.c:456
It appears that the reason for the crash is that get_remote_heads()
(called from transport_get_remote_refs() through
get_refs_via_connect()) returns NULL in list.
Here's my log from stepping through get_remote_heads:
Breakpoint 3, get_remote_heads (in=7, list=0x27fc28, nr_match=0, match=0x0,
flags=0, extra_have=0x27a127c) at connect.c:59
59 *list = NULL;
(gdb) n
67 len = packet_read_line(in, buffer, sizeof(buffer));
(gdb) n
68 if (!len)
(gdb) n
101 return list;
(gdb) n
102 }
(gdb) p list
$13 = (struct ref **) 0x27fc28
(gdb) p list
$14 = (struct ref **) 0x27fc28
(gdb) n
get_refs_via_connect (transport=0x27a1218, for_push=0) at transport.c:640
640 return refs;
(gdb) p refs
$15 = (struct ref *) 0x0
It looks to me like we're failing to read anything from the network
here and don't handle the error correctly, but I don't understand the
code well enough to tell for sure.
My best guess would be that a fix could be something like this, but
I'm not really 100% sure. Doing so makes "git remote show
<remote-name" display something like this
$ /git/git remote show origin_new
* remote remote-name
URL: USER@HOST:REPONAME.git
HEAD branch: (unknown)
Which I guess makes sense, since I haven't made any branches on that repo yet.
diff --git a/builtin-remote.c b/builtin-remote.c
index 2ed752c..9ff4b3f 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -793,6 +793,7 @@ static int get_remote_ref_states(const char *name,
states->remote->url[0] : NULL);
remote_refs = transport_get_remote_refs(transport);
transport_disconnect(transport);
+ if (!remote_refs) return 0;
states->queried = 1;
if (query & GET_REF_STATES)
--
Erik "kusma" Faye-Lund
kusmabite@gmail.com
(+47) 986 59 656
next reply other threads:[~2009-05-25 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 16:10 Erik Faye-Lund [this message]
2009-05-25 19:01 ` Segfault in "git remote show <remote-name>" Clemens Buchacher
2009-05-26 14:27 ` Jay Soffian
2009-05-27 20:13 ` [PATCH 1/2] fix segfault showing an empty remote Clemens Buchacher
2009-05-27 20:13 ` [PATCH 2/2] match_refs: search ref list tail internally Clemens Buchacher
2009-05-28 7:06 ` Junio C Hamano
2009-05-28 9:26 ` Clemens Buchacher
2009-05-31 14:26 ` [PATCH v2] " Clemens Buchacher
2009-05-26 18:54 ` Segfault in "git remote show <remote-name>" Erik Faye-Lund
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=40aa078e0905250910v268faa66p29a0183db26cb0df@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=git@vger.kernel.org \
/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).