From: Derrick Stolee <stolee@gmail.com>
To: "René Scharfe" <l.s.r@web.de>, "Git Mailing List" <git@vger.kernel.org>
Cc: Derrick Stolee <dstolee@microsoft.com>,
Jeff Hostetler <jeffhost@microsoft.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] cleanup: fix possible overflow errors in binary search, part 2
Date: Thu, 13 Jun 2019 14:06:00 -0400 [thread overview]
Message-ID: <ac09e504-369d-d6d5-a356-07a75386d3fb@gmail.com> (raw)
In-Reply-To: <f0059613-d3e4-a1e2-2c01-727579e069d2@web.de>
On 6/13/2019 1:51 PM, René Scharfe wrote:
> Calculating the sum of two array indexes to find the midpoint between
> them can overflow, i.e. code like this is unsafe for big arrays:
>
> mid = (first + last) >> 1;
>
> Make sure the intermediate value stays within the boundaries instead,
> like this:
>
> mid = first + ((last - first) >> 1);
>
> The loop condition of the binary search makes sure that 'last' is
> always greater than 'first', so this is safe as long as 'first' is
> not negative. And that can be verified easily using the pre-context
> of each change, except for name-hash.c, so add an assertion to that
> effect there.
>
> The unsafe calculations were found with:
>
> git grep '(.*+.*) *>> *1'
>
> This is a continuation of 19716b21a4 (cleanup: fix possible overflow
> errors in binary search, 2017-10-08).
Thank you for finding these additional examples!
LGTM. Pretty easy to see this is correct.
-Stolee
next prev parent reply other threads:[~2019-06-13 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 17:51 [PATCH] cleanup: fix possible overflow errors in binary search, part 2 René Scharfe
2019-06-13 18:06 ` Derrick Stolee [this message]
2019-06-13 19:42 ` Martin Ågren
2019-06-13 21:33 ` René Scharfe
2019-06-14 4:18 ` Martin Ågren
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=ac09e504-369d-d6d5-a356-07a75386d3fb@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox