From f4865e39dd0bcae7e5f3f5d59807d6ac9a8a99ba Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Thu, 29 Aug 2024 16:56:20 +0200 Subject: dashboard/config/linux: bump lockdep consts even more Btrfs needs higher values to avoid false positives: https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/ --- dashboard/config/linux/bits/lockdep.yml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'dashboard/config/linux/bits') diff --git a/dashboard/config/linux/bits/lockdep.yml b/dashboard/config/linux/bits/lockdep.yml index 03aa31ba6..8a6eb236a 100644 --- a/dashboard/config/linux/bits/lockdep.yml +++ b/dashboard/config/linux/bits/lockdep.yml @@ -4,13 +4,15 @@ config: - LOCKDEP # This helps to preent "BUG: MAX_LOCKDEP_ENTRIES too low!" - - LOCKDEP_BITS: [17, v5.13] + # Note: btrfs requires quite high values for these to avoid false positives: + # https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/ + - LOCKDEP_BITS: [20, v5.13] # This helps to prevent "BUG: MAX_LOCKDEP_CHAINS too low!" # and "BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!" - # We don't set it to 18 on arm64, because in that case the -full config does not boot on GCE. + # We don't set it to 20 on arm64, because in that case the -full config does not boot on GCE. # It boots with 17, but the kconf syntax currently does not let us set it to 17 for some arches - # and to 18 for others. - - LOCKDEP_CHAINS_BITS: [18, v5.13, -arm64] + # and to 20 for others. + - LOCKDEP_CHAINS_BITS: [20, v5.13, -arm64] - LOCKDEP_STACK_TRACE_BITS: [20, v5.13] - LOCKDEP_STACK_TRACE_HASH_BITS: [14, v5.13] - LOCKDEP_CIRCULAR_QUEUE_BITS: [12, v5.13] -- cgit mrf-deployment