All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Srujith A Poojary via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Phillip Wood <phillip.wood123@gmail.com>,
	 Srujith A Poojary <poojarysrujith@gmail.com>
Subject: Re: [PATCH v3] diff-delta: use safe integer arithmetic
Date: Sat, 24 Oct 2026 09:15:49 -0700	[thread overview]
Message-ID: <xmqqfqxv13d6.fsf@gitster.g> (raw)
In-Reply-To: <pull.2276.v3.git.1792813697888.gitgitgadget@gmail.com> (Srujith A. Poojary via GitGitGadget's message of "Sat, 24 Oct 2026 03:48:17 +0000")

"Srujith A Poojary via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> From: Srujith A Poojary <poojarysrujith@gmail.com>
>
> Replace manual multiplication and addition in create_delta_index()
> with safe integer helpers (st_mult, st_add, st_add3) to prevent potential
> overflows when computing memory allocation sizes.
>
> On 32-bit platforms, struct alignment padding could cause the total
> allocation size calculation to exceed 2^32, making safe integer arithmetic
> necessary.

I wonder if "X could cause Y" above skips a bit too many steps.  I
was expecting more along the lines of ...

    We will need to allocate N instances of A and M instances of B, N
    and M are capped to X and Y respectively by this code

        ... code snippet ...

    and size of an instance of A is 8 and size of B could be either W or
    Z.  When size of B is W, then the total allocation would be ...

And that analysis applies only on the first allocation.  I didn't
even look at the packed side of the allocation size, expecting that
you would know how to analyze after seeing my example on the other
allocation.

> Note that hsize + 1 inside st_add3() is safe from overflow
> because hsize is capped at 2^26 early in the function.

It is misleading to say hsize+1 is inside st_add3(), though.


> diff --git a/diff-delta.c b/diff-delta.c
> index 7cbedeb507..efebce3aca 100644
> --- a/diff-delta.c
> +++ b/diff-delta.c
> @@ -162,8 +162,8 @@ struct delta_index * create_delta_index(const void *buf, size_t bufsize)
>  	hmask = hsize - 1;
>  
>  	/* allocate lookup index */
> -	memsize = sizeof(*hash) * hsize +
> -		  sizeof(*entry) * entries;
> +	memsize = st_add(st_mult(sizeof(*hash), hsize),
> +			 st_mult(sizeof(*entry), entries));
>  	mem = malloc(memsize);
>  	if (!mem)
>  		return NULL;
> @@ -258,9 +258,9 @@ struct delta_index * create_delta_index(const void *buf, size_t bufsize)
>  	 * Now create the packed index in array form
>  	 * rather than linked lists.
>  	 */
> -	memsize = sizeof(*index)
> -		+ sizeof(*packed_hash) * (hsize+1)
> -		+ sizeof(*packed_entry) * entries;
> +	memsize = st_add3(sizeof(*index),
> +			  st_mult(sizeof(*packed_hash), hsize + 1),
> +			  st_mult(sizeof(*packed_entry), entries));
>  	mem = malloc(memsize);
>  	if (!mem) {
>  		free(hash);
>
> base-commit: 47fdf2208c5b94c8cc01c106b8f7c85efb91c926

  reply	other threads:[~2026-10-24 16:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  3:56 [PATCH] [Outreachy PATCH] diff-delta: use safe integer arithmetic Srujith A Poojary via GitGitGadget
2026-10-23  5:04 ` Junio C Hamano
2026-10-23  5:29   ` Srujith Poojary
2026-10-23 15:30     ` Junio C Hamano
2026-10-23 16:56       ` Srujith Poojary
2026-10-23 18:45         ` Junio C Hamano
2026-10-23  5:56 ` [PATCH v2] " Srujith A Poojary via GitGitGadget
2026-10-23 15:15   ` Phillip Wood
2026-10-23 18:49     ` Junio C Hamano
2026-10-24  3:44       ` Srujith Poojary
2026-10-24  3:48 ` [PATCH v3] " Srujith A Poojary via GitGitGadget
2026-10-24 16:15   ` Junio C Hamano [this message]
2026-10-24 17:26     ` Srujith Poojary
2026-10-25 18:10       ` Junio C Hamano
2026-10-25 19:21         ` Srujith Poojary
2026-10-24 18:00 ` [PATCH v4] " Srujith A Poojary via GitGitGadget
2026-10-25 19:20 ` [PATCH v5] " Srujith A Poojary via GitGitGadget
2026-10-26 17:37   ` Junio C Hamano
2026-10-26 18:47     ` Srujith Poojary
2026-10-27  4:50     ` Srujith Poojary
2026-10-27  4:51 ` [PATCH v6] " Srujith A Poojary via GitGitGadget
2026-10-27 10:33   ` Pablo Sabater
2026-10-27 11:01     ` Srujith Poojary
2026-10-27 11:32       ` Pablo Sabater
2026-10-27 11:00 ` [PATCH v7] " Srujith A Poojary via GitGitGadget
2026-10-27 11:52   ` Pablo Sabater
2026-10-27 14:18     ` Srujith Poojary
2026-10-27 16:27     ` Junio C Hamano
2026-10-27 16:57       ` Srujith Poojary
2026-10-27 14:21 ` [PATCH v8] " Srujith A Poojary via GitGitGadget
2026-10-27 16:56 ` [PATCH v9] " Srujith A Poojary 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=xmqqfqxv13d6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=poojarysrujith@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 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.