From 6b36d33868a01cea153c3a9cca05aef3548e4aea Mon Sep 17 00:00:00 2001
From: Dmitry Vyukov <dvyukov@google.com>
Date: Mon, 30 Dec 2019 11:41:20 +0100
Subject: syz-manager: corpus rotation

Use a random subset of syscalls/corpus/coverage for each individual VM run.
Hypothesis is that this should allow fuzzer to get more coverage
find more bugs in saturated state (stuck in local optimum).
See the issue and comments for details.

Update #1348
---
 pkg/signal/signal.go | 7 -------
 1 file changed, 7 deletions(-)

(limited to 'pkg/signal')

diff --git a/pkg/signal/signal.go b/pkg/signal/signal.go
index 20deba46a..d6fa8d459 100644
--- a/pkg/signal/signal.go
+++ b/pkg/signal/signal.go
@@ -4,10 +4,6 @@
 // Package signal provides types for working with feedback signal.
 package signal
 
-import (
-	"sort"
-)
-
 type (
 	elemType uint32
 	prioType int8
@@ -163,9 +159,6 @@ type Context struct {
 }
 
 func Minimize(corpus []Context) []interface{} {
-	sort.Slice(corpus, func(i, j int) bool {
-		return corpus[i].Signal.Len() > corpus[j].Signal.Len()
-	})
 	type ContextPrio struct {
 		prio prioType
 		idx  int
-- 
cgit mrf-deployment