Branch: refs/heads/gh-readonly-queue/master/pr-7537-fb92f11c4789d9647a75c09c983dbee5c8488ccf
Home:
https://github.com/google/syzkaller
Commit: 6a0c72dc19b6aed338462dcb11d299092801d530
https://github.com/google/syzkaller/commit/6a0c72dc19b6aed338462dcb11d299092801d530
Author: Aleksandr Nogikh <
nog...@google.com>
Date: 2026-06-29 (Mon, 29 Jun 2026)
Changed paths:
M pkg/rpcserver/rpcserver.go
M pkg/rpcserver/runner.go
M pkg/runtest/executor_test.go
Log Message:
-----------
pkg/rpcserver: inject keepalive requests when VM is idle
When the fuzzer queue is empty and executions are rare, the host side
timeout in vm.go ("no output from test machine") can falsely trigger.
This happens because lastExecuteTime is only updated when the host
receives an ExecutingMessage from the VM, which never occurs if no
programs are being sent.
Add an explicit handleIdle routine in Runner.ConnectionLoop. If the
queue is completely empty for more than 10 seconds, send a dummy program
(0 calls) to the VM. This forces the executor's fork server to spawn a
process, reply with an ExecutingMessage, and bump the monitor's timer.
This safely proves the VM and the executor pipeline are alive without
creating false timeouts.
To unsubscribe from these emails, change your notification settings at
https://github.com/google/syzkaller/settings/notifications