From c0ced5570c6505a80235b64884c93e89733b77f3 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Tue, 20 Apr 2021 07:22:30 +0200 Subject: dashboard/config/linux: bump LOCKDEP_STACK_TRACE_BITS Once we've bumped other capacity values, "BUG: MAX_STACK_TRACE_ENTRIES too low!" started happening as well: https://syzkaller.appspot.com/bug?id=4ebb151b4e3ef885165669fea5b4cf1f2e353ab0 https://groups.google.com/g/syzkaller-upstream-moderation/c/8FK5kogGHM4 Bump LOCKDEP_STACK_TRACE_BITS by 1. --- dashboard/config/linux/bits/debug.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'dashboard/config/linux/bits/debug.yml') diff --git a/dashboard/config/linux/bits/debug.yml b/dashboard/config/linux/bits/debug.yml index 012922e70..07ceac405 100644 --- a/dashboard/config/linux/bits/debug.yml +++ b/dashboard/config/linux/bits/debug.yml @@ -9,7 +9,7 @@ config: - LOCKDEP - LOCKDEP_BITS: [16, linux-next] - LOCKDEP_CHAINS_BITS: [17, linux-next] - - LOCKDEP_STACK_TRACE_BITS: [19, linux-next] + - LOCKDEP_STACK_TRACE_BITS: [20, linux-next] - LOCKDEP_STACK_TRACE_HASH_BITS: [14, linux-next] - LOCKDEP_CIRCULAR_QUEUE_BITS: [12, linux-next] - PROVE_LOCKING -- cgit mrf-deployment