From b6605ba8b96835063c5eb766c38d27fac98b84d4 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Mon, 13 Oct 2025 09:51:44 +0200 Subject: pkg/report: skip crypto frames for KMSAN reports This bug is at least one case where we merge several different KMSAN reports because they end up being triggered in the same generic code: https://syzkaller.appspot.com/bug?id=6290a184e96e8fb4b657700adcd243ef195113e1 Skip some common symbols from crypto/ so that the titles become more specific. --- pkg/report/linux.go | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'pkg/report/linux.go') diff --git a/pkg/report/linux.go b/pkg/report/linux.go index c97e31bc4..fdf960015 100644 --- a/pkg/report/linux.go +++ b/pkg/report/linux.go @@ -1511,7 +1511,11 @@ var linuxOopses = append([]*oops{ compile("(Local variable .* created at:|Uninit was created at:)"), parseStackTrace, }, - skip: []string{"alloc_skb", "netlink_ack", "netlink_rcv_skb"}, + skip: []string{ + "alloc_skb", "netlink_ack", "netlink_rcv_skb", + // Encryption routines are the place where we hit the bug, but + // the generic code is a bad candidate for bug titles. + "_encrypt$", "^(?:crypto|cipher|drbg|rng)_"}, }, noStackTrace: true, }, -- cgit mrf-deployment