From: Stefan Beller <stefanbeller@gmail.com>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCH 1/2] transport: Free leaking head in transport_print_push_status
Date: Mon, 20 Oct 2014 18:50:44 -0700 [thread overview]
Message-ID: <1413856245-5443-1-git-send-email-stefanbeller@gmail.com> (raw)
From: Stefan Beller <sbeller@google.com>
Found by scan.coverity.com (ID: 1248110)
Signed-off-by: Stefan Beller <sbeller@google.com>
---
transport.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/transport.c b/transport.c
index 055d2a2..fbab6ee 100644
--- a/transport.c
+++ b/transport.c
@@ -774,6 +774,7 @@ void transport_print_push_status(const char *dest, struct ref *refs,
*reject_reasons |= REJECT_NEEDS_FORCE;
}
}
+ free(head);
}
void transport_verify_remote_names(int nr_heads, const char **heads)
--
2.1.2.332.g8071e93
next reply other threads:[~2014-10-21 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 1:50 Stefan Beller [this message]
2014-10-21 1:50 ` [PATCH 2/2] .mailmap: Add Stefan Bellers corporate mail address Stefan Beller
2014-10-21 5:53 ` Junio C Hamano
[not found] ` <CAGZ79kYNvQOKLZ5qgCD1NyYG8X2q7UCr5rMbrxW6ajRAnFRz7A@mail.gmail.com>
2014-10-22 22:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1413856245-5443-1-git-send-email-stefanbeller@gmail.com \
--to=stefanbeller@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@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).