From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH 1/2] malloc: fix an over-allocation bug
Date: Mon, 16 Apr 2018 18:40:42 -0400 [thread overview]
Message-ID: <20180416224042.GB3094@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180416175436.2384-1-amonakov@ispras.ru>
On Mon, Apr 16, 2018 at 08:54:35PM +0300, Alexander Monakov wrote:
> Fix an instance where realloc code would overallocate by OVERHEAD bytes
> amount. Manually arrange for reuse of memcpy-free-return exit sequence.
> ---
> src/malloc/malloc.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/src/malloc/malloc.c b/src/malloc/malloc.c
> index 9e05e1d6..1af4ae5a 100644
> --- a/src/malloc/malloc.c
> +++ b/src/malloc/malloc.c
> @@ -397,10 +397,9 @@ void *realloc(void *p, size_t n)
> size_t newlen = n + extra;
> /* Crash on realloc of freed chunk */
> if (extra & 1) a_crash();
> - if (newlen < PAGE_SIZE && (new = malloc(n))) {
> - memcpy(new, p, n-OVERHEAD);
> - free(p);
> - return new;
> + if (newlen < PAGE_SIZE && (new = malloc(n-OVERHEAD))) {
> + n0 = n;
> + goto copy_free_ret;
> }
> newlen = (newlen + PAGE_SIZE-1) & -PAGE_SIZE;
> if (oldlen == newlen) return p;
> @@ -443,6 +442,7 @@ copy_realloc:
> /* As a last resort, allocate a new chunk and copy to it. */
> new = malloc(n-OVERHEAD);
> if (!new) return 0;
> +copy_free_ret:
> memcpy(new, p, n0-OVERHEAD);
> free(CHUNK_TO_MEM(self));
> return new;
Looks ok. I've got this queued as submitted.
Rich
prev parent reply other threads:[~2018-04-16 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 17:54 Alexander Monakov
2018-04-16 17:54 ` [PATCH 2/2] ldso, malloc: implement reclaim_gaps via __malloc_donate Alexander Monakov
2018-04-16 22:39 ` Rich Felker
2018-04-17 5:30 ` Alexander Monakov
2018-04-17 15:57 ` Rich Felker
2018-04-17 17:06 ` Rich Felker
2018-04-17 19:01 ` Rich Felker
2018-04-17 20:52 ` Alexander Monakov
2018-04-17 22:21 ` Rich Felker
2018-04-16 22:40 ` Rich Felker [this message]
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=20180416224042.GB3094@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).