linux-kernel - MAX_LOCKDEP_CHAINS too low! (sysfs?)

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>] [day] [month] [year] [list]

Date:	Fri, 18 Oct 2013 09:47:52 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Cc:	Al Viro <viro@...iv.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg Kroah-Hartman <greg@...ah.com>
Subject: MAX_LOCKDEP_CHAINS too low! (sysfs?)

BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
Please attach the output of /proc/lock_stat to the bug report
CPU: 1 PID: 2102862 Comm: trinity-main Not tainted 3.12.0-rc5+ #27
Hardware name: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H/GA-MA78GM-S2H, BIOS F12a 04/23/2010
 ffffffff82427e90 ffff88006f9cd938 ffffffff816db90c 000000000104c014
 ffff88006f9cda00 ffffffff810c40cd ffffffff810bf11e ffff88006f9cd970
 ffffffff810bf645 ffff8800c9ee1550 ffff88012a000a18 00007fffce3189e8
Call Trace:
 [<ffffffff816db90c>] dump_stack+0x4e/0x82
 [<ffffffff810c40cd>] __lock_acquire+0x1b6d/0x1bd0
 [<ffffffff810bf11e>] ? put_lock_stats.isra.28+0xe/0x40
 [<ffffffff810bf645>] ? lock_release_holdtime.part.29+0xe5/0x160
 [<ffffffff810d04f2>] ? __module_text_address+0x12/0x60
 [<ffffffff810d4b1f>] ? is_module_text_address+0x2f/0x60
 [<ffffffff8106e580>] ? __kernel_text_address+0x50/0x70
 [<ffffffff81006507>] ? print_context_stack+0x87/0xf0
 [<ffffffff810c48d3>] lock_acquire+0x93/0x1e0
 [<ffffffff816d95d7>] ? get_partial_node.isra.41+0x49/0x20a
 [<ffffffff816e4441>] _raw_spin_lock+0x41/0x80
 [<ffffffff816d95d7>] ? get_partial_node.isra.41+0x49/0x20a
 [<ffffffff816d95d7>] get_partial_node.isra.41+0x49/0x20a
 [<ffffffff810c13b7>] ? check_usage_backwards+0x87/0x150
 [<ffffffff816d9918>] __slab_alloc+0x180/0x4dd
 [<ffffffff810c1330>] ? print_shortest_lock_dependencies+0x1d0/0x1d0
 [<ffffffff81249ea8>] ? sysfs_open_file+0xb8/0x230
 [<ffffffff810bf086>] ? __lock_is_held+0x56/0x80
 [<ffffffff811a304c>] kmem_cache_alloc_trace+0x2dc/0x3a0
 [<ffffffff81249ea8>] ? sysfs_open_file+0xb8/0x230
 [<ffffffff81249ea8>] sysfs_open_file+0xb8/0x230
 [<ffffffff811c129b>] do_dentry_open+0x25b/0x310
 [<ffffffff812dfcbc>] ? security_inode_permission+0x1c/0x30
 [<ffffffff81249df0>] ? sysfs_schedule_callback+0x1e0/0x1e0
 [<ffffffff811c1399>] finish_open+0x49/0x60
 [<ffffffff811d3af4>] do_last+0x5b4/0x1200
 [<ffffffff811d480e>] path_openat+0xce/0x6b0
 [<ffffffff8100b324>] ? native_sched_clock+0x24/0x80
 [<ffffffff811d5577>] do_filp_open+0x47/0xa0
 [<ffffffff811e4daf>] ? __alloc_fd+0xaf/0x200
 [<ffffffff811c2829>] do_sys_open+0x139/0x220
 [<ffffffff81010b95>] ? syscall_trace_enter+0x155/0x2a0
 [<ffffffff811c292e>] SyS_open+0x1e/0x20
 [<ffffffff816ed9e4>] tracesys+0xdd/0xe2


/proc/lock_stat is at http://www.codemonkey.org.uk/junk/locks-2013-10-18.txt

Probably not going to get time to dig into this before kernel summit,
but posting in case it's something obvious..

	Dave

--
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/