From 66f22a7fdccb93f261cc260d0f5965dbbdcc0073 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Sat, 7 Apr 2018 14:02:03 +0200 Subject: syz-manager: don't abort on disabled syscalls It turns out to be too difficult to specify a precise set of syscalls when, say, all setsockopt's for some sockets need to be enabled, but not enabled for other sockets. Just warn user about disabled syscalls, but don't abort. --- syz-manager/manager.go | 5 ----- 1 file changed, 5 deletions(-) diff --git a/syz-manager/manager.go b/syz-manager/manager.go index 564d04f2d..b0256c06f 100644 --- a/syz-manager/manager.go +++ b/syz-manager/manager.go @@ -952,17 +952,12 @@ func (mgr *Manager) Check(a *CheckArgs, r *int) error { for _, dc := range a.DisabledCalls { disabled[dc.Name] = dc.Reason } - fail := false for _, id := range mgr.enabledSyscalls { name := mgr.target.Syscalls[id].Name if reason := disabled[name]; reason != "" { Logf(0, "disabling %v: %v", name, reason) - fail = true } } - if fail { - Fatalf("some syscalls enabled by enable_syscalls can't be enabled") - } } mgr.vmChecked = true mgr.enabledCalls = a.Calls -- cgit mrf-deployment