All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Lidong Yan via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "René Scharfe" <l.s.r@web.de>,
	"Lidong Yan" <502024330056@smail.nju.edu.cn>
Subject: Re: [PATCH v2] REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macro
Date: Fri, 9 May 2025 08:51:41 +0200	[thread overview]
Message-ID: <aB2l_WaBFyz5POld@pks.im> (raw)
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:
> 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

  reply	other threads:[~2025-05-09  6:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 13:39 [PATCH] REFTABLE_REALLOC_ARRAY: fix potential memory leak if realloc failed Lidong Yan via GitGitGadget
2025-05-08 21:42 ` René Scharfe
2025-05-09  1:54   ` lidongyan
2025-05-09  3:43   ` Junio C Hamano
2025-05-09  2:04 ` [PATCH v2] REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macro Lidong Yan via GitGitGadget
2025-05-09  6:51   ` Patrick Steinhardt [this message]
2025-05-09  7:38     ` lidongyan
2025-05-09  7:44   ` [PATCH v3] " Lidong Yan via GitGitGadget
2025-05-09  8:23     ` Patrick Steinhardt
2025-05-09 14:25       ` Junio C Hamano

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=aB2l_WaBFyz5POld@pks.im \
    --to=ps@pks.im \
    --cc=502024330056@smail.nju.edu.cn \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=l.s.r@web.de \
    /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.