linux-kernel - Re: 2.6.33-rc3-mmotm0106 - BUG: MAX_LOCKDEP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 13 Jan 2010 14:28:08 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Valdis.Kletnieks@...edu
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.33-rc3-mmotm0106 - BUG: MAX_LOCKDEP_KEYS too low!

On Wed, 2010-01-13 at 01:22 -0500, Valdis.Kletnieks@...edu wrote:
> Seen in my dmesg output - I wasn't even home at the time, so my
> laptop was basically idle.
> 
> [ 7777.019267] dell-wmi: Received unknown WMI event (0x11)
> [ 8190.620401] BUG: MAX_LOCKDEP_KEYS too low!

> If I'm hitting MAX_LOCKDEP_KEYS after just a few hours on a mostly-idle
> laptop, should it be set higher?

I'm wondering what's eating all those classes, it there a lot of module
loading/unloading happening?

Does something like the below give any clues?

---
diff --git a/kernel/lockdep.c b/kernel/lockdep.c
index 5feaddc..90b9428 100644
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -761,6 +761,7 @@ register_lock_class(struct lockdep_map *lock,
unsigned int subclass, int force)
 	debug_atomic_inc(&nr_unused_locks);
 	class->key = key;
 	class->name = lock->name;
+	printk(KERN_EMERG "LOCK CLASS: %s\n", lock->name);
 	class->subclass = subclass;
 	INIT_LIST_HEAD(&class->lock_entry);
 	INIT_LIST_HEAD(&class->locks_before);


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/