Messages in this thread Patch in this message | | | From | Daniel Vetter <> | Subject | [PATCH 2/2] lockdep: Up MAX_LOCKDEP_CHAINS | Date | Wed, 29 Nov 2017 16:41:45 +0100 |
| |
cross-release ftl
From Chris:
"Fwiw, this isn't cross-release but us reloading the module many times, creating a whole host of new lockclasses. Even more fun is when the module gets a slightly different address and the new lock address hashes into an old lock...
"I did think about a module-hook to revoke the stale lockclasses, but that still leaves all the hashed chains.
"This particular nuisance was temporarily pushed back by teaching igt not to reload i915.ko on a whim."
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Marta Lofstedt <marta.lofstedt@intel.com> References: https://bugs.freedesktop.org/show_bug.cgi?id=103707 Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> --- kernel/locking/lockdep_internals.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/lockdep_internals.h b/kernel/locking/lockdep_internals.h index d459d624ba2a..41630a5385c6 100644 --- a/kernel/locking/lockdep_internals.h +++ b/kernel/locking/lockdep_internals.h @@ -69,7 +69,7 @@ enum { #else #define MAX_LOCKDEP_ENTRIES 32768UL -#define MAX_LOCKDEP_CHAINS_BITS 16 +#define MAX_LOCKDEP_CHAINS_BITS 17 /* * Stack-trace: tightly packed array of stack backtrace -- 2.15.0
| |