From 56d87229fad9ebee9698d3e78d5cd6a9b6f12fe9 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Fri, 18 Jul 2025 17:58:49 +0200 Subject: pkg/report: exclude crc implementations from guilty files If these happen to be in the stack frames, in almost all cases it will be due to a bug in the calling code. See the discussion in #5784. --- pkg/report/linux.go | 2 ++ 1 file changed, 2 insertions(+) (limited to 'pkg/report/linux.go') diff --git a/pkg/report/linux.go b/pkg/report/linux.go index c67274ac8..c97e31bc4 100644 --- a/pkg/report/linux.go +++ b/pkg/report/linux.go @@ -110,6 +110,8 @@ func ctorLinux(cfg *config) (reporterImpl, []string, error) { regexp.MustCompile(`^fs/proc/generic.c`), regexp.MustCompile(`^trusty/`), // Trusty sources are not in linux kernel tree. regexp.MustCompile(`^drivers/usb/core/urb.c`), // WARNING in urb.c usually means a bug in a driver + // Crashes in these files are almost always caused by the calling code. + regexp.MustCompile(`^arch/.*/lib/crc.*`), } ctx.guiltyLineIgnore = regexp.MustCompile(`(hardirqs|softirqs)\s+last\s+(enabled|disabled)|^Register r\d+ information`) // These pattern do _not_ start a new report, i.e. can be in a middle of another report. -- cgit mrf-deployment