From: Keith Packard <keithp@keithp.com>
To: newlib@sourceware.org
Subject: [PATCH 1/2] libm/stdlib: don't read past source in nano_realloc
Date: Thu, 13 Aug 2020 17:19:01 -0700 [thread overview]
Message-ID: <20200814001902.510489-2-keithp@keithp.com> (raw)
In-Reply-To: <20200814001902.510489-1-keithp@keithp.com>
Save the computed block size and use it to avoid reading past
the end of the source block.
Signed-off-by: Keith Packard <keithp@keithp.com>
---
newlib/libc/stdlib/nano-mallocr.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/newlib/libc/stdlib/nano-mallocr.c b/newlib/libc/stdlib/nano-mallocr.c
index 04465eb9e..5028431ec 100644
--- a/newlib/libc/stdlib/nano-mallocr.c
+++ b/newlib/libc/stdlib/nano-mallocr.c
@@ -466,6 +466,7 @@ void * nano_realloc(RARG void * ptr, malloc_size_t size)
{
void * mem;
chunk * p_to_realloc;
+ malloc_size_t old_size;
if (ptr == NULL) return nano_malloc(RCALL size);
@@ -477,13 +478,14 @@ void * nano_realloc(RARG void * ptr, malloc_size_t size)
/* TODO: There is chance to shrink the chunk if newly requested
* size is much small */
- if (nano_malloc_usable_size(RCALL ptr) >= size)
+ old_size = nano_malloc_usable_size(RCALL ptr);
+ if (old_size >= size)
return ptr;
mem = nano_malloc(RCALL size);
if (mem != NULL)
{
- memcpy(mem, ptr, size);
+ memcpy(mem, ptr, old_size);
nano_free(RCALL ptr);
}
return mem;
--
2.28.0
next prev parent reply other threads:[~2020-08-14 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 0:19 [PATCH 0/2] Realloc fixes version 2 Keith Packard
2020-08-14 0:19 ` Keith Packard [this message]
2020-08-14 0:19 ` [PATCH 2/2] libm/stdlib: Realloc when shrinking by 2* or more Keith Packard
2020-08-17 9:45 ` [PATCH 0/2] Realloc fixes version 2 Corinna Vinschen
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=20200814001902.510489-2-keithp@keithp.com \
--to=keithp@keithp.com \
--cc=newlib@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).