libbpf: Set MFD_NOEXEC_SEAL when creating memfd #8298
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 105ff53 ("mm/memfd: add MFD_NOEXEC_SEAL and MFD_EXEC"), the kernel has started printing a warning if neither MFD_NOEXEC_SEAL nor MFD_EXEC is set in memfd_create().
To avoid this warning (and also be more secure), set MFD_NOEXEC_SEAL by default. But since libbpf can be running on potentially very old kernels, leave a fallback for kernels without MFD_NOEXEC_SEAL support.