From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Stefan Beller <sbeller@google.com>, Jeff King <peff@peff.net>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCHv4 1/4] notes: don't leak memory in git_config_get_notes_strategy
Date: Fri, 01 Apr 2016 09:12:43 -0700 [thread overview]
Message-ID: <xmqqh9fljojo.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAPig+cQ=83k-of=jP1r6bYqsYrUhiDKhR3_Bm-SfYndn+sL=Dg@mail.gmail.com> (Eric Sunshine's message of "Thu, 31 Mar 2016 20:46:15 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> Meh. Rather than reverting the git_config_get_value(), it would have
> been just as easy and safer (less chance of a future change
> re-introducing a leak) if you had just inserted the necessary check
> here:
>
> if (!value)
> return config_error_nonbool(key);
Yup, sounds much more sensible fix that is useful in the longer term
(and avoids one unnecessary strdup()).
>
> But, perhaps it's not worth the patch churn at this point...
>
>> if (parse_notes_merge_strategy(value, strategy))
>> git_die_config(key, "unknown notes merge strategy %s", value);
>>
>> + free(value);
>> return 0;
>> }
>>
>> --
>> 2.5.0.264.gc776916.dirty
next prev parent reply other threads:[~2016-04-01 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 0:35 [PATCHv4 0/4] Some cleanups Stefan Beller
2016-04-01 0:35 ` [PATCHv4 1/4] notes: don't leak memory in git_config_get_notes_strategy Stefan Beller
2016-04-01 0:46 ` Eric Sunshine
2016-04-01 16:12 ` Junio C Hamano [this message]
2016-04-01 17:03 ` Junio C Hamano
2016-04-01 17:14 ` Jeff King
2016-04-01 17:30 ` Eric Sunshine
2016-04-01 0:35 ` [PATCHv4 2/4] abbrev_sha1_in_line: don't leak memory Stefan Beller
2016-04-01 0:35 ` [PATCHv4 3/4] bundle: don't leak an fd in case of early return Stefan Beller
2016-04-01 17:05 ` Junio C Hamano
2016-04-01 17:15 ` Jeff King
2016-04-01 17:29 ` Junio C Hamano
2016-04-01 17:31 ` Jeff King
2016-04-01 0:35 ` [PATCHv4 4/4] credential-cache, send_request: close fd when done Stefan Beller
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=xmqqh9fljojo.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.