From 1e35461e020a8b43c7b2d79ee64eb4068a9f0481 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Fri, 8 Nov 2019 07:50:44 +0100 Subject: pkg/report: trim panic_on_warn set few lines earlier The KCSAN reports can be quite short. Now with task contexts we can hopefully reduce the threshold a bit. --- pkg/report/linux.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'pkg/report/linux.go') diff --git a/pkg/report/linux.go b/pkg/report/linux.go index f57011fed..bc21900a7 100644 --- a/pkg/report/linux.go +++ b/pkg/report/linux.go @@ -251,7 +251,7 @@ func (ctx *linux) findReport(output []byte, oops *oops, startPos int, context st // from other CPUs regardless of what is the current context. // Otherwise we will throw traceback away because it does not match the oops context. cpuTraceback = true - } else if textLines > 25 && + } else if textLines > 22 && (bytes.Contains(line, []byte("Kernel panic - not syncing")) || bytes.Contains(line, []byte("WARNING: possible circular locking dependency detected"))) { // If panic_on_warn set, then we frequently have 2 stacks: -- cgit mrf-deployment