[google/syzkaller] a6f99a: pkg/rpcserver: move kernel test/data range checks ...

[Dmitry Vyukov]

Branch: refs/heads/gh-readonly-queue/master/pr-4955-1f0ee43044bc8fc00bc1eccc85a93bf2b9972dd1
Home: https://github.com/google/syzkaller
Commit: a6f99ace4014896f81a2f101416fd5413579f2bd
https://github.com/google/syzkaller/commit/a6f99ace4014896f81a2f101416fd5413579f2bd
Author: Dmitry Vyukov <dvy...@google.com>
Date: 2024-07-01 (Mon, 01 Jul 2024)

Changed paths:
M executor/common_test.h
M executor/executor.cc
M executor/executor_bsd.h
M executor/executor_darwin.h
M executor/executor_linux.h
M executor/executor_runner.h
M executor/executor_test.h
M executor/nocover.h
M pkg/flatrpc/flatrpc.fbs
M pkg/flatrpc/flatrpc.go
M pkg/flatrpc/flatrpc.h
M pkg/rpcserver/local.go
M pkg/rpcserver/rpcserver.go
M pkg/rpcserver/runner.go
M pkg/runtest/executor_test.go
M pkg/runtest/run_test.go
M sys/targets/targets.go
M sys/test/exec.txt

Log Message:
-----------
pkg/rpcserver: move kernel test/data range checks from executor

We see some errors of the form:

SYZFAIL: coverage filter is full
pc=0x80007000c0008 regions=[0xffffffffbfffffff 0x243fffffff 0x143fffffff 0xc3fffffff] alloc=156

Executor shouldn't send non kernel addresses in signal,
but somehow it does. It can happen if the VM memory is corrupted,
or if the test program does something very nasty (e.g. discovers
the output region and writes to it).

It's not possible to reliably filter signal in the tested VM.
Move all of the filtering logic to the host.

Fixes #4942



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

[Dmitry Vyukov]

Branch: refs/heads/master