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

Re: [PATCHv4 1/4] notes: don't leak memory in git_config_get_notes_strategy

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 1, 2016, 16:12 UTC
Message-ID
<xmqqh9fljojo.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAPig+cQ=83k-of=jP1r6bYqsYrUhiDKhR3_Bm-SfYndn+sL=Dg@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 7 quoted lines
> 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()).

Show 12 quoted lines
>
> 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
Previous: Eric SunshineNext: Junio C Hamano
Message 4 of 14 in “[PATCHv4 0/4] Some cleanups”
  1. Stefan BellerApr 1, 2016
  2. 1/4 notes: don't leak memory in git_config_get_notes_strategyStefan Beller, Apr 1, 2016
  3. Eric SunshineApr 1, 2016
  4. Junio C HamanoApr 1, 2016
  5. Junio C HamanoApr 1, 2016
  6. Jeff KingApr 1, 2016
  7. Eric SunshineApr 1, 2016
  8. 2/4 abbrev_sha1_in_line: don't leak memoryStefan Beller, Apr 1, 2016
  9. 3/4 bundle: don't leak an fd in case of early returnStefan Beller, Apr 1, 2016
  10. Junio C HamanoApr 1, 2016
  11. Jeff KingApr 1, 2016
  12. Junio C HamanoApr 1, 2016
  13. Jeff KingApr 1, 2016
  14. 4/4 credential-cache, send_request: close fd when doneStefan Beller, Apr 1, 2016

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.