2023-11-01 12:56:05 +00:00
|
|
|
/* Utilities functions to name memory mappings.
|
2024-01-01 18:12:26 +00:00
|
|
|
Copyright (C) 2023-2024 Free Software Foundation, Inc.
|
2023-11-01 12:56:05 +00:00
|
|
|
This file is part of the GNU C Library.
|
|
|
|
|
|
|
|
|
|
The GNU C Library is free software; you can redistribute it and/or
|
|
|
|
|
modify it under the terms of the GNU Lesser General Public
|
|
|
|
|
License as published by the Free Software Foundation; either
|
|
|
|
|
version 2.1 of the License, or (at your option) any later version.
|
|
|
|
|
|
|
|
|
|
The GNU C Library is distributed in the hope that it will be useful,
|
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
|
Lesser General Public License for more details.
|
|
|
|
|
|
|
|
|
|
You should have received a copy of the GNU Lesser General Public
|
|
|
|
|
License along with the GNU C Library; if not, see
|
|
|
|
|
<https://www.gnu.org/licenses/>. */
|
|
|
|
|
|
|
|
|
|
#include <ldsodefs.h>
|
|
|
|
|
#include <setvmaname.h>
|
|
|
|
|
#include <sys/prctl.h>
|
|
|
|
|
#include <sysdep.h>
|
elf: Add glibc.mem.decorate_maps tunable
The PR_SET_VMA_ANON_NAME support is only enabled through a configurable
kernel switch, mainly because assigning a name to a
anonymous virtual memory area might prevent that area from being
merged with adjacent virtual memory areas.
For instance, with the following code:
void *p1 = mmap (NULL,
1024 * 4096,
PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS,
-1,
0);
void *p2 = mmap (p1 + (1024 * 4096),
1024 * 4096,
PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS,
-1,
0);
The kernel will potentially merge both mappings resulting in only one
segment of size 0x800000. If the segment is names with
PR_SET_VMA_ANON_NAME with different names, it results in two mappings.
Although this will unlikely be an issue for pthread stacks and malloc
arenas (since for pthread stacks the guard page will result in
a PROT_NONE segment, similar to the alignment requirement for the arena
block), it still might prevent the mmap memory allocated for detail
malloc.
There is also another potential scalability issue, where the prctl
requires
to take the mmap global lock which is still not fully fixed in Linux
[1] (for pthread stacks and arenas, it is mitigated by the stack
cached and the arena reuse).
So this patch disables anonymous mapping annotations as default and
add a new tunable, glibc.mem.decorate_maps, can be used to enable
it.
[1] https://lwn.net/Articles/906852/
Checked on x86_64-linux-gnu and aarch64-linux-gnu.
Reviewed-by: DJ Delorie <dj@redhat.com>
2023-11-01 12:56:11 +00:00
|
|
|
#include <elf/dl-tunables.h>
|
2023-11-01 12:56:05 +00:00
|
|
|
|
|
|
|
|
/* If PR_SET_VMA_ANON_NAME is not supported by the kernel, prctl returns
|
|
|
|
|
EINVAL. However, it also returns the same error for invalid argument.
|
|
|
|
|
Since it is an internal-only API, it assumes well formatted input:
|
|
|
|
|
aligned START, with (START, START+LEN) being a valid memory range,
|
|
|
|
|
and NAME with a limit of 80 characters without invalid one ("\\`$[]"). */
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
__set_vma_name (void *start, size_t len, const char *name)
|
|
|
|
|
{
|
|
|
|
|
static int prctl_supported = 1;
|
|
|
|
|
if (atomic_load_relaxed (&prctl_supported) == 0)
|
|
|
|
|
return;
|
|
|
|
|
|
elf: Add glibc.mem.decorate_maps tunable
The PR_SET_VMA_ANON_NAME support is only enabled through a configurable
kernel switch, mainly because assigning a name to a
anonymous virtual memory area might prevent that area from being
merged with adjacent virtual memory areas.
For instance, with the following code:
void *p1 = mmap (NULL,
1024 * 4096,
PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS,
-1,
0);
void *p2 = mmap (p1 + (1024 * 4096),
1024 * 4096,
PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS,
-1,
0);
The kernel will potentially merge both mappings resulting in only one
segment of size 0x800000. If the segment is names with
PR_SET_VMA_ANON_NAME with different names, it results in two mappings.
Although this will unlikely be an issue for pthread stacks and malloc
arenas (since for pthread stacks the guard page will result in
a PROT_NONE segment, similar to the alignment requirement for the arena
block), it still might prevent the mmap memory allocated for detail
malloc.
There is also another potential scalability issue, where the prctl
requires
to take the mmap global lock which is still not fully fixed in Linux
[1] (for pthread stacks and arenas, it is mitigated by the stack
cached and the arena reuse).
So this patch disables anonymous mapping annotations as default and
add a new tunable, glibc.mem.decorate_maps, can be used to enable
it.
[1] https://lwn.net/Articles/906852/
Checked on x86_64-linux-gnu and aarch64-linux-gnu.
Reviewed-by: DJ Delorie <dj@redhat.com>
2023-11-01 12:56:11 +00:00
|
|
|
/* Set the prctl as not supported to avoid checking the tunable on every
|
|
|
|
|
call. */
|
|
|
|
|
if (TUNABLE_GET (glibc, mem, decorate_maps, int32_t, NULL) != 0)
|
|
|
|
|
{
|
|
|
|
|
int r = INTERNAL_SYSCALL_CALL (prctl, PR_SET_VMA, PR_SET_VMA_ANON_NAME,
|
|
|
|
|
start, len, name);
|
|
|
|
|
if (r == 0 || r != -EINVAL)
|
|
|
|
|
return;
|
|
|
|
|
}
|
2023-11-01 12:56:05 +00:00
|
|
|
atomic_store_relaxed (&prctl_supported, 0);
|
|
|
|
|
return;
|
|
|
|
|
}
|
