[google/syzkaller] dce63a: executor: change input/output area mapping rules

6 views
Skip to first unread message

Aleksandr Nogikh

unread,
Aug 5, 2025, 8:34:09 AM8/5/25
to syzk...@googlegroups.com
Branch: refs/heads/gh-readonly-queue/master/pr-6251-904e669cc2b1488495dbffa4c066e54b77edd910
Home: https://github.com/google/syzkaller
Commit: dce63a35b1bfe856335d8334bcd75f5412157309
https://github.com/google/syzkaller/commit/dce63a35b1bfe856335d8334bcd75f5412157309
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2025-08-05 (Tue, 05 Aug 2025)

Changed paths:
M executor/executor.cc

Log Message:
-----------
executor: change input/output area mapping rules

For ASAN builds, assume that the executable is dynamically linked and
that the addresses in HighMem may be occupied by the libraries.

Otherwise, use fixed addresses both for the input and the output area.
Before, input area was mapped at an arbitrary location and the default
output area location for ASAN builds was sometimes overlapping with it.

Use MAP_FIXED_NOREPLACE to prevent such overlappings in the first place.


Commit: 0931f9bfa8eacf9840a2bd3f9def3cfb4349431e
https://github.com/google/syzkaller/commit/0931f9bfa8eacf9840a2bd3f9def3cfb4349431e
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2025-08-05 (Tue, 05 Aug 2025)

Changed paths:
M sys/targets/targets.go

Log Message:
-----------
sys/targets: enable ASAN for TestArch64Fuzz

Now it no longer causes a segfault.


Compare: https://github.com/google/syzkaller/compare/dce63a35b1bf%5E...0931f9bfa8ea

To unsubscribe from these emails, change your notification settings at https://github.com/google/syzkaller/settings/notifications

Aleksandr Nogikh

unread,
Aug 5, 2025, 8:45:53 AM8/5/25
to syzk...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages