diff options
| author | Marco Vanotti <mvanotti@google.com> | 2019-08-30 08:30:37 -0700 |
|---|---|---|
| committer | Marco Vanotti <mvanotti@users.noreply.github.com> | 2019-09-11 16:38:45 -0300 |
| commit | f4e53c1037f48d9bf1790df955b0cc7028a7008e (patch) | |
| tree | 2ac5ccb868f725829e4682767ce828d305aad5aa /executor/test_linux.h | |
| parent | 000d39a9b8d9273a5b09d9f07aea4952107afafa (diff) | |
executor/fuchsia: don't crash on syz_mmap failure.
syz_mmap is a pseudo-syscall that can be used by syzkaller in fuzzing
programs, however, it is also used to setup the environment for
syz-executor. syz-executor already checks the return value[0] when it is
used for setting up the environment, so it doesn't make sense for the
function to crash (most probably, in a fuzzing program it will be called
with arguments that would make it fail).
The previous behavior was causing a bunch of "Lost connection to test
machine" syzkaller crashes which were meaningless. An example of a
program in which syz_mmap would crash would be any program in which the
handle to the root vmar is closed before calling syz_mmap.
[0]:
https://github.com/google/syzkaller/blob/a60cb4cd840ce786236a00480e8bb1025e0c5fef/executor/executor_fuchsia.h#L15
Diffstat (limited to 'executor/test_linux.h')
0 files changed, 0 insertions, 0 deletions