aboutsummaryrefslogtreecommitdiff
path: root/elf/dl-tunables.c
diff options
context:
space:
mode:
authorAdhemerval Zanella <adhemerval.zanella@linaro.org>2021-11-03 11:20:50 -0300
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2021-11-09 14:11:25 -0300
commitb05fae4d8e34604a72ee36d2d3164391b76fcf0b (patch)
treea66b3f943d6b70b27326261fcb60063378e4c67f /elf/dl-tunables.c
parentdb6c4935fae6005d46af413b32aa92f4f6059dce (diff)
downloadglibc-b05fae4d8e34604a72ee36d2d3164391b76fcf0b.tar
glibc-b05fae4d8e34604a72ee36d2d3164391b76fcf0b.tar.gz
glibc-b05fae4d8e34604a72ee36d2d3164391b76fcf0b.tar.bz2
glibc-b05fae4d8e34604a72ee36d2d3164391b76fcf0b.zip
elf: Use the minimal malloc on tunables_strdup
The rtld_malloc functions are moved to its own file so it can be used on csu code. Also, the functiosn are renamed to __minimal_* (since there are now used not only on loader code). Using the __minimal_malloc on tunables_strdup() avoids potential issues with sbrk() calls while processing the tunables (I see sporadic elf/tst-dso-ordering9 on powerpc64le with different tests failing due ASLR). Also, using __minimal_malloc over plain mmap optimizes the memory allocation on both static and dynamic case (since it will any unused space in either the last page of data segments, avoiding mmap() call, or from the previous mmap() call). Checked on x86_64-linux-gnu, i686-linux-gnu, and powerpc64le-linux-gnu. Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Diffstat (limited to 'elf/dl-tunables.c')
-rw-r--r--elf/dl-tunables.c7
1 files changed, 4 insertions, 3 deletions
diff --git a/elf/dl-tunables.c b/elf/dl-tunables.c
index 1666736bc1..497e948f1c 100644
--- a/elf/dl-tunables.c
+++ b/elf/dl-tunables.c
@@ -31,6 +31,7 @@
#include <fcntl.h>
#include <ldsodefs.h>
#include <array_length.h>
+#include <dl-minimal-malloc.h>
#define TUNABLES_INTERNAL 1
#include "dl-tunables.h"
@@ -48,13 +49,13 @@ tunables_strdup (const char *in)
size_t i = 0;
while (in[i++] != '\0');
- char *out = __sbrk (i);
+ char *out = __minimal_malloc (i + 1);
/* For most of the tunables code, we ignore user errors. However,
this is a system error - and running out of memory at program
startup should be reported, so we do. */
- if (out == (void *)-1)
- _dl_fatal_printf ("sbrk() failure while processing tunables\n");
+ if (out == NULL)
+ _dl_fatal_printf ("failed to allocate memory to process tunables\n");
while (i-- > 0)
out[i] = in[i];