From 3f9ec663653495bfaeeb0a2f2dfce01f2820bb01 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Thu, 13 Dec 2018 12:22:49 +0100 Subject: pkg/report: relaxed gvisor OOM suppressions Existing ones don't match actual gvisor output after address mangling. Not matching exact context in parens should be good enough re false positives. --- pkg/report/gvisor.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'pkg/report/gvisor.go') diff --git a/pkg/report/gvisor.go b/pkg/report/gvisor.go index f4b478929..c2d33f7e2 100644 --- a/pkg/report/gvisor.go +++ b/pkg/report/gvisor.go @@ -22,9 +22,9 @@ func ctorGvisor(target *targets.Target, kernelSrc, kernelObj string, suppressions := []string{ "fatal error: runtime: out of memory", "fatal error: runtime: cannot allocate memory", - "panic: ptrace sysemu failed: no such process", // OOM kill - `panic: ptrace set fpregs \(&{.*}\) failed: no such process`, // OOM kill - `panic: ptrace set regs \(&{.*}\) failed: no such process`, // OOM kill + "panic: ptrace sysemu failed: no such process", // OOM kill + `panic: ptrace set fpregs \(.*\) failed: no such process`, // OOM kill + `panic: ptrace set regs \(.*\) failed: no such process`, // OOM kill "panic: failed to start executor binary", "panic: executor failed: pthread_create failed", "panic: error mapping run data: error mapping runData: cannot allocate memory", -- cgit mrf-deployment