From: Eric Sunshine <sunshine@sunshineco.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Elia Pinto <gitter.spiros@gmail.com>,
Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] ident.c: add support for IPv6
Date: Fri, 30 Oct 2015 14:19:06 -0400 [thread overview]
Message-ID: <CAPig+cQkWc+R2vEn9DBdKVcsNNEWELCNNOMksBDxF7A5dTPHkQ@mail.gmail.com> (raw)
In-Reply-To: <5633A838.3070801@web.de>
On Fri, Oct 30, 2015 at 1:26 PM, Torsten Bögershausen <tboegi@web.de> wrote:
> On 2015-10-30 15.48, Elia Pinto wrote:
>> Add IPv6 support by implementing name resolution with the
>> ---
>> +#ifndef NO_IPV6
>> +
>> +static void add_domainname(struct strbuf *out)
>> +{
>> + char buf[1024];
>> + struct addrinfo hints, *ai;
>> + int gai;
> The scope of these variables can be narrowed, by moving them into the "{" block,
> where they are needed. (Before the memset())
>> +
>> + if (gethostname(buf, sizeof(buf))) {
>> + warning("cannot get host name: %s", strerror(errno));
>> + strbuf_addstr(out, "(none)");
>> + return;
>> + }
>> + if (strchr(buf, '.'))
>> + strbuf_addstr(out, buf);
>> + else {
> Many ' ' between else and '{', one should be enough
>> + memset (&hints, '\0', sizeof (hints));
>> + hints.ai_flags = AI_CANONNAME;
>> + if (!(gai = getaddrinfo(buf, NULL, &hints, &ai)) && ai && strchr(ai->ai_canonname, '.')) {
Why is 'gai' needed and assigned? It's value is never consulted thereafter.
>> + strbuf_addstr(out, ai->ai_canonname);
>> + freeaddrinfo(ai);
Also, aren't you leaking 'ai' when 'ai_canonname' doesn't contain a '.'?
>> + }
>> + else
> Colud be written in one line as "} else"
>> + strbuf_addf(out, "%s.(none)", buf);
>> + }
>> +}
>> +#else /* NO_IPV6 */
next prev parent reply other threads:[~2015-10-30 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 14:48 [PATCH] ident.c: add support for IPv6 Elia Pinto
2015-10-30 17:26 ` Torsten Bögershausen
2015-10-30 18:13 ` Junio C Hamano
2015-10-30 18:19 ` Eric Sunshine [this message]
2015-10-30 18:29 ` Jeff King
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=CAPig+cQkWc+R2vEn9DBdKVcsNNEWELCNNOMksBDxF7A5dTPHkQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--cc=peff@peff.net \
--cc=tboegi@web.de \
/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).