From a7ae31ed14a28ec2501e4113578ef3cee6020a75 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Thu, 19 Nov 2020 10:35:03 +0100 Subject: vm: pass Report to Diagnose The way to diagnose generally depends on the issue. E.g. do we need register dump to debug this issue? Do we need host dmesg dump? Some diagnosis may be directly specific to a particular problem (e.g. dumping a particular debugfs/procfs file). Pass Report to Diagnose to make this possible. --- vm/vmware/vmware.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'vm/vmware') diff --git a/vm/vmware/vmware.go b/vm/vmware/vmware.go index 25f4eb4ec..ebfb995bb 100644 --- a/vm/vmware/vmware.go +++ b/vm/vmware/vmware.go @@ -17,6 +17,7 @@ import ( "github.com/google/syzkaller/pkg/config" "github.com/google/syzkaller/pkg/log" "github.com/google/syzkaller/pkg/osutil" + "github.com/google/syzkaller/pkg/report" "github.com/google/syzkaller/vm/vmimpl" ) @@ -217,6 +218,6 @@ func (inst *instance) Run(timeout time.Duration, stop <-chan bool, command strin return vmimpl.Multiplex(cmd, merger, dmesg, timeout, stop, inst.closed, inst.debug) } -func (inst *instance) Diagnose() ([]byte, bool) { +func (inst *instance) Diagnose(rep *report.Report) ([]byte, bool) { return nil, false } -- cgit mrf-deployment