linux-kernel - Re: 2.6.34-rc1: ACPI: BUG: key f71f0168 not in .data!

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

Date:	Tue, 9 Mar 2010 08:40:25 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Alexander Beregalov <a.beregalov@...il.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Greg KH <gregkh@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.34-rc1: ACPI: BUG: key f71f0168 not in .data!

On Mon, Mar 08, 2010 at 04:32:36PM -0800, Yinghai Lu wrote:
>> [  145.239329] BUG: key ffff88206fe99c58 not in .data!
>> [  145.244994] ------------[ cut here ]------------
>> [  145.250949] WARNING: at kernel/lockdep.c:2706 lockdep_init_map+0xf1/0x53c()
>> [  145.267543] Modules linked in:
>> [  145.275078] Pid: 1, comm: swapper Not tainted 2.6.34-rc1-yh-dirty #221
>> [  145.285140] Call Trace:
>> [  145.290143]  [<ffffffff810759b0>] warn_slowpath_common+0x7c/0x94
>> [  145.304624]  [<ffffffff810759dc>] warn_slowpath_null+0x14/0x16
>> [  145.314632]  [<ffffffff8109f299>] lockdep_init_map+0xf1/0x53c
>> [  145.325228]  [<ffffffff8117e100>] ? sysfs_new_dirent+0x8f/0x104
>> [  145.334331]  [<ffffffff8117d72e>] sysfs_add_file_mode+0x66/0xac
>> [  145.339850]  [<ffffffff8117d785>] sysfs_add_file+0x11/0x13
>> [  145.355513]  [<ffffffff8117d844>] sysfs_create_file+0x2a/0x2c
>> [  145.360637]  [<ffffffff8148ca98>] device_create_file+0x19/0x1b
>> [  145.375187]  [<ffffffff8145fc9a>] ipmi_register_smi+0x862/0xd72
>> [  145.384606]  [<ffffffff8148b9f8>] ? put_device+0x17/0x19
>> [  145.395142]  [<ffffffff8148cee5>] ? device_add+0x44b/0x52a
>> [  145.403666]  [<ffffffff8108fb5a>] ? autoremove_wake_function+0x0/0x39
>> [  145.416309]  [<ffffffff81462e71>] try_smi_init+0x6d0/0x8a0
>> [  145.424534]  [<ffffffff81ba2fd5>] init_ipmi_si+0x4cf/0x907
>> [  145.434799]  [<ffffffff81ba2b06>] ? init_ipmi_si+0x0/0x907
>> [  145.439677]  [<ffffffff8100020d>] do_one_initcall+0x72/0x17f
>> [  145.455681]  [<ffffffff826836a0>] kernel_init+0x166/0x1f0
>> [  145.463319]  [<ffffffff81032914>] kernel_thread_helper+0x4/0x10
>> [  145.476497]  [<ffffffff81bfc2bc>] ? restore_args+0x0/0x30
>> [  145.485014]  [<ffffffff8268353a>] ? kernel_init+0x0/0x1f0
>> [  145.495859]  [<ffffffff81032910>] ? kernel_thread_helper+0x0/0x10
>> [  145.501541] ---[ end trace 0ec12b1482c47368 ]---
>
>related to ?
>commit a2db6842873c8e5a70652f278d469128cb52db70

Yes. Need to add sysfs_attr_init() or sysfs_bin_attr_init() in the
driver code.

-- 
Live like a child, think like the god.
 
--
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/