linux-kernel - ia64 lockdep: trying to register non-static key (mm->mmap

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

Message-ID: <3877989d0911251943j6860e88ci93e237ba65835bc7@mail.gmail.com>
Date:	Thu, 26 Nov 2009 11:43:36 +0800
From:	Luming Yu <luming.yu@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	"Luck, Tony" <tony.luck@...el.com>, Ingo Molnar <mingo@...e.hu>
Subject: ia64 lockdep: trying to register non-static key (mm->mmap_sem)

Anybody know how I should do to fix the lockdep
warning below, which is triggered in
ia64_brk doing "down_write(&mm->mmap_sem)"

Any comments are appreciated.


INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.

Call Trace:
 [<a000000100017330>] show_stack+0x70/0xc0
                                sp=e0000004807a7c50 bsp=e0000004807a1c78
 [<a0000001000173d0>] dump_stack+0x50/0x80
                                sp=e0000004807a7e20 bsp=e0000004807a1c58
 [<a0000001000f7ca0>] __lock_acquire+0x1a0/0x13e0
                                sp=e0000004807a7e20 bsp=e0000004807a1bc0
 [<a0000001000fc310>] lock_acquire+0x170/0x1e0
                                sp=e0000004807a7e20 bsp=e0000004807a1b60
 [<a0000001008338d0>] down_write+0x70/0x180
                                sp=e0000004807a7e20 bsp=e0000004807a1b28
 [<a00000010003b960>] ia64_brk+0x60/0x280
                                sp=e0000004807a7e20 bsp=e0000004807a1aa0
 [<a00000010000c620>] ia64_ret_from_syscall+0x0/0x20


Thanks,
Luming
--
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/