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

Re: [PATCH v2] REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macro

From
Patrick Steinhardt <ps@pks.im>
Date
May 9, 2025, 06:51 UTC
Message-ID
<aB2l_WaBFyz5POld@pks.im>
In-Reply-To
<pull.1955.v2.git.git.1746756263207.gitgitgadget@gmail.com>
On Fri, May 09, 2025 at 02:04:22AM +0000, Lidong Yan via GitGitGadget wrote:
Show 20 quoted lines
> diff --git a/reftable/basics.h b/reftable/basics.h
> index d8888c12629..667feffd935 100644
> --- a/reftable/basics.h
> +++ b/reftable/basics.h
> @@ -199,16 +199,8 @@ static inline int reftable_alloc_size(size_t nelem, size_t elsize, size_t *out)
>  			(x) = reftable_malloc(alloc_size); \
>  		} \
>  	} while (0)
> -#define REFTABLE_CALLOC_ARRAY(x, alloc) (x) = reftable_calloc((alloc), sizeof(*(x)))
> -#define REFTABLE_REALLOC_ARRAY(x, alloc) do { \
> -		size_t alloc_size; \
> -		if (reftable_alloc_size(sizeof(*(x)), (alloc), &alloc_size) < 0) { \
> -			errno = ENOMEM; \
> -			(x) = NULL; \
> -		} else { \
> -			(x) = reftable_realloc((x), alloc_size); \
> -		} \
> -	} while (0)
> +#define REFTABLE_CALLOC_ARRAY(x, alloc) \
> +	(x) = reftable_calloc((alloc), sizeof(*(x)))

Let's avoid reformatting unrelated macros. But other than that I fully agree -- we should remove stuff that we don't use in the first place.

Thanks!
Patrick
Previous: Lidong Yan via GitGitGadgetNext: lidongyan
Message 6 of 10 in “REFTABLE_REALLOC_ARRAY: fix potential memory leak if realloc failed”
  1. REFTABLE_REALLOC_ARRAY: fix potential memory leak if realloc failedLidong Yan via GitGitGadget, May 8, 2025
  2. René ScharfeMay 8, 2025
  3. lidongyanMay 9, 2025
  4. Junio C HamanoMay 9, 2025
  5. REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macroLidong Yan via GitGitGadget, May 9, 2025
  6. Patrick SteinhardtMay 9, 2025
  7. lidongyanMay 9, 2025
  8. REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macroLidong Yan via GitGitGadget, May 9, 2025
  9. Patrick SteinhardtMay 9, 2025
  10. Junio C HamanoMay 9, 2025

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.