Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

executor: favor MAP_FIXED_NOREPLACE over MAP_FIXED #5741

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

a-nogikh
Copy link
Collaborator

@a-nogikh a-nogikh commented Feb 4, 2025

MAP_FIXED_NOREPLACE allows to fail early if we happened to overlap with an existing memory mapping. It should help detects bugs like #5674 at an earlier stage, before it led to memory corruptions.

MAP_FIXED_NOREPLACE is supported from Linux 4.17, which is okay for all syzkaller use cases on syzbot.

There's no such option for some of the supported OSes, so set it depending on the configuration we're building for.

MAP_FIXED_NOREPLACE allows to fail early if we happened to overlap with
an existing memory mapping. It should help detects bugs google#5674 at an
earlier stage, before it led to memory corruptions.

MAP_FIXED_NOREPLACE is supported from Linux 4.17, which is okay for all
syzkaller use cases on syzbot.

There's no such option for some of the supported OSes, so set it
depending on the configuration we're building for.
@a-nogikh a-nogikh requested a review from dvyukov February 4, 2025 11:19
@a-nogikh a-nogikh added this pull request to the merge queue Feb 4, 2025
Merged via the queue into google:master with commit 39e250d Feb 4, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants