From 6ef3e47010676e4e159edb346c219e8d30cabadc Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Thu, 23 May 2024 10:13:32 +0200 Subject: syz-fuzzer: repair leak checking Notify fuzzer from the manager when corpus triage has finished to start leak checking. Fixes #4728 --- pkg/flatrpc/flatrpc.fbs | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'pkg/flatrpc/flatrpc.fbs') diff --git a/pkg/flatrpc/flatrpc.fbs b/pkg/flatrpc/flatrpc.fbs index cdddef965..5b211bb31 100644 --- a/pkg/flatrpc/flatrpc.fbs +++ b/pkg/flatrpc/flatrpc.fbs @@ -76,6 +76,7 @@ table FeatureInfoRaw { union HostMessagesRaw { ExecRequest :ExecRequestRaw, SignalUpdate :SignalUpdateRaw, + StartLeakChecks :StartLeakChecksRaw } table HostMessageRaw { @@ -160,6 +161,12 @@ table SignalUpdateRaw { drop_max :[uint64]; } +// Leak checking is very slow so we don't do it while triaging the corpus +// (otherwise it takes infinity). This message serves as a signal that +// the corpus was triaged and the fuzzer can start leak checking. +table StartLeakChecksRaw { +} + // Notification from the executor that it started executing the program 'id'. // We want this request to be as small and as fast as possible b/c we need it // to reach the host (or at least leave the VM) before the VM crashes -- cgit mrf-deployment