From: Junio C Hamano <gitster@pobox.com>
To: "Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Edward Thomson <ethomson@edwardthomson.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH 2/3] xdiff: refactor a function
Date: Wed, 09 Feb 2022 22:28:16 -0800 [thread overview]
Message-ID: <xmqq8rujxmkf.fsf@gitster.g> (raw)
In-Reply-To: <xmqqmtiz9aro.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 09 Feb 2022 10:04:43 -0800")
Junio C Hamano <gitster@pobox.com> writes:
>> int xdl_merge(mmfile_t *orig, mmfile_t *mf1, mmfile_t *mf2,
>> xmparam_t const *xmp, mmbuffer_t *result)
>> {
>> - xdchange_t *xscr1, *xscr2;
>> - xdfenv_t xe1, xe2;
>> - int status;
>> + xdchange_t *xscr1 = NULL, *xscr2 = NULL;
>> + xdfenv_t xe1 = { 0 }, xe2 = { 0 };
>> + int status = -1;
>> xpparam_t const *xpp = &xmp->xpp;
>>
>> result->ptr = NULL;
>> result->size = 0;
>>
>> - if (xdl_do_diff(orig, mf1, xpp, &xe1) < 0) {
>> - return -1;
>> - }
>> - if (xdl_do_diff(orig, mf2, xpp, &xe2) < 0) {
>> - xdl_free_env(&xe1);
>> - return -1;
>> - }
>
> OK, xdl_do_diff() calls xdl_free_env(xe) before an error return (I
> didn't check if patience and histogram also do so correctly), so the
> original was not leaking xe1 or xe2.
After I wrote the above, I took a brief look at patience and histogram,
and it does not seem to release resources held by "env" when it signals
a failure by returning a negative value. So it seems that the original
used with patience or histogram were leaking env when it failed, and
this patch plugs that small leak.
If that is indeed the case, please note it in the proposed log
message.
Thanks.
next prev parent reply other threads:[~2022-02-10 6:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:59 [PATCH 0/3] xdiff: handle allocation failures Phillip Wood via GitGitGadget
2022-02-09 10:59 ` [PATCH 1/3] xdiff: handle allocation failure in patience diff Phillip Wood via GitGitGadget
2022-02-09 10:59 ` [PATCH 2/3] xdiff: refactor a function Phillip Wood via GitGitGadget
2022-02-09 18:04 ` Junio C Hamano
2022-02-10 6:28 ` Junio C Hamano [this message]
2022-02-11 15:19 ` Phillip Wood
2022-02-11 16:46 ` Junio C Hamano
2022-02-09 10:59 ` [PATCH 3/3] xdiff: handle allocation failure when merging Phillip Wood via GitGitGadget
2022-02-16 10:15 ` [PATCH v2 0/4] xdiff: handle allocation failures Phillip Wood via GitGitGadget
2022-02-16 10:15 ` [PATCH v2 1/4] xdiff: fix a memory leak Phillip Wood via GitGitGadget
2022-02-16 10:28 ` Ævar Arnfjörð Bjarmason
2022-02-16 13:49 ` Phillip Wood
2022-02-16 14:38 ` Ævar Arnfjörð Bjarmason
2022-02-16 16:55 ` Junio C Hamano
2022-02-17 11:05 ` Phillip Wood
2022-02-16 10:15 ` [PATCH v2 2/4] xdiff: handle allocation failure in patience diff Phillip Wood via GitGitGadget
2022-02-16 10:15 ` [PATCH v2 3/4] xdiff: refactor a function Phillip Wood via GitGitGadget
2022-02-16 10:15 ` [PATCH v2 4/4] xdiff: handle allocation failure when merging Phillip Wood via GitGitGadget
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=xmqq8rujxmkf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ethomson@edwardthomson.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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).