mirror of
https://github.com/reactos/syzkaller.git
synced 2024-10-07 09:03:28 +00:00
c3e9afb345
Fuchsia has strict controls over who can map memory as executable. Refactoring syz-executor to be able to do that involves a non trivial amount of work: it needs to run as a fuchsia component and replace stdin for some other mechanism to communicate with syz-fuzzer (probably a fidl service and a thin client that proxies stdin/stdout to syz-fuzzer via ssh). Mapping memory as executable doesn't seem to be used or needed in syz-executor at all. After talking with Dmitry, he mentioned that it was used in a deprecated feature: `syz_execute_func` which would execute random code. It also allows more scenarios during fuzzing. For now, I'm removing that option to allow syzkaller continue fuzzing. This change also refactors all of the error messages adding a string representation of the `zx_status_t` in error logs. |
||
|---|---|---|
| .. | ||
| ast | ||
| bisect | ||
| build | ||
| cmdprof | ||
| compiler | ||
| config | ||
| cover | ||
| csource | ||
| db | ||
| gce | ||
| gcs | ||
| hash | ||
| host | ||
| html | ||
| ifuzz | ||
| instance | ||
| ipc | ||
| kd | ||
| log | ||
| mgrconfig | ||
| osutil | ||
| report | ||
| repro | ||
| rpctype | ||
| runtest | ||
| serializer | ||
| signal | ||
| symbolizer | ||
| vcs | ||