diff options
| author |   Daniel Xu <dxu@dxuuu.xyz> | 2024-12-30 14:31:22 -0700 |
|---|---|---|
| committer |   Alexei Starovoitov <ast@kernel.org> | 2024-12-30 14:48:15 -0800 |
| commit | 1846dd8e3a3e28f58e72cadbf4d81f374e63a085 (patch) | |
| tree | 90e443c891db2101e6923d458a24f6d72f08295b /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | selftests/bpf: Clear out Python syntax warnings (diff) | |
| download | linux-rng-1846dd8e3a3e28f58e72cadbf4d81f374e63a085.tar.xz linux-rng-1846dd8e3a3e28f58e72cadbf4d81f374e63a085.zip | |
libbpf: Set MFD_NOEXEC_SEAL when creating memfd
Starting from 105ff5339f49 ("mm/memfd: add MFD_NOEXEC_SEAL and
MFD_EXEC") and until 1717449b4417 ("memfd: drop warning for missing
exec-related flags"), the kernel would print a warning if neither
MFD_NOEXEC_SEAL nor MFD_EXEC is set in memfd_create().
If libbpf runs on on a kernel between these two commits (eg. on an
improperly backported system), it'll trigger this warning.
To avoid this warning (and also be more secure), explicitly set
MFD_NOEXEC_SEAL. But since libbpf can be run on potentially very old
kernels, leave a fallback for kernels without MFD_NOEXEC_SEAL support.
Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
Link: https://lore.kernel.org/r/6e62c2421ad7eb1da49cbf16da95aaaa7f94d394.1735594195.git.dxu@dxuuu.xyz
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions