Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  peff@peff.net,  newren@gmail.com,
	 Derrick Stolee <stolee@gmail.com>
Subject: Re: [PATCH 4/6] strbuf-safe: add sstrbuf_grow()
Date: Mon, 21 Sep 2026 14:29:57 -0700	[thread overview]
Message-ID: <xmqqv77yl2cq.fsf@gitster.g> (raw)
In-Reply-To: <ebd91b95209d778727dca1bfcce17dcb76b3151f.1789736540.git.gitgitgadget@gmail.com> (Derrick Stolee via GitGitGadget's message of "Fri, 18 Sep 2026 13:02:18 +0000")

"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:

> +int srealloc(void **ptr, size_t size)
>  {
>  	if (!size) {
> +		free(*ptr);
> +		if ((*ptr = malloc(1)))
> +			return 0;
> +		return -1;
>  	}
>  
> +	if (safe_memory_limit_check(size, 0))
> +		return -1;
> +	if ((*ptr = realloc(*ptr, size)))
> +		return 0;
> +
> +	return -1;
> +}

This overrites *ptr with whatever realloc() returns, and then checks
if we had an error, thereby losing whatever pointer *ptr originally
had.  When realloc() does fail, we have already clobbered *ptr, and
very likely have robbed our caller the pointer it had to the region
of memory.  Aren't we leaking that piece of memory as the result?

  reply	other threads:[~2026-09-21 21:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 13:02 [PATCH 0/6] [RFC] Create a 'safe' strbuf API Derrick Stolee via GitGitGadget
2026-09-18 13:02 ` [PATCH 1/6] strbuf: add header for 'safe' API Derrick Stolee via GitGitGadget
2026-09-21 21:18   ` Junio C Hamano
2026-09-23 19:25   ` Mark C. Chu-Carroll
2026-09-23 20:14     ` Junio C Hamano
2026-09-18 13:02 ` [PATCH 2/6] wrapper: initialize GIT_ALLOC_LIMIT proactively Derrick Stolee via GitGitGadget
2026-09-18 13:02 ` [PATCH 3/6] wrapper: create safe_memory_limit_check() Derrick Stolee via GitGitGadget
2026-09-21 21:24   ` Junio C Hamano
2026-09-18 13:02 ` [PATCH 4/6] strbuf-safe: add sstrbuf_grow() Derrick Stolee via GitGitGadget
2026-09-21 21:29   ` Junio C Hamano [this message]
2026-09-18 13:02 ` [PATCH 5/6] json-writer: include strbuf-safe.h Derrick Stolee via GitGitGadget
2026-09-18 13:02 ` [PATCH 6/6] strbuf-safe: add init and release methods Derrick Stolee via GitGitGadget
2026-09-21 21:44   ` Junio C Hamano
2026-09-21 22:34     ` Junio C Hamano
2026-09-19 15:23 ` [PATCH 0/6] [RFC] Create a 'safe' strbuf API Phillip Wood
2026-09-23 19:46   ` Jeff King
2026-10-06 14:33     ` Derrick Stolee

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=xmqqv77yl2cq.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    --cc=stolee@gmail.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