linux-kernel - [bug] fixed_init(): BUG: at drivers/base/core.c:120 device_release(), was: "2.6.21-rc5: known regressions"

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20070330120657.GA21271@elte.hu>
Date:	Fri, 30 Mar 2007 14:06:57 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>
Subject: [bug] fixed_init(): BUG: at drivers/base/core.c:120 device_release(), was: "2.6.21-rc5: known regressions"

there's a new type of message in allyesconfig-bzImage bootup test:

Calling initcall 0xc1b6d692: fixed_init+0x0/0x33()
Fixed PHY: Registered new driver
Device 'fixed@100:1' does not have a release() function, it is broken and must be fixed.
BUG: at drivers/base/core.c:120 device_release()
 [<c0105ff9>] show_trace_log_lvl+0x19/0x2e
 [<c01063e2>] show_trace+0x12/0x14
 [<c01063f8>] dump_stack+0x14/0x16
 [<c063cddf>] device_release+0x7c/0x7e
 [<c0476c32>] kobject_cleanup+0x44/0x5e
 [<c0476c57>] kobject_release+0xb/0xd
 [<c04773ef>] kref_put+0x63/0x71
 [<c0476757>] kobject_put+0x14/0x16
 [<c063ceef>] put_device+0x11/0x13
 [<c063d943>] device_unregister+0x12/0x15
 [<c07337d1>] fixed_mdio_register_device+0x210/0x23b
 [<c1b6d6b0>] fixed_init+0x1e/0x33
 [<c1b31a2d>] init+0x15d/0x2bd
 [<c0105bc3>] kernel_thread_helper+0x7/0x10
 =======================
Device 'fixed@10:1' does not have a release() function, it is broken and must be fixed.
BUG: at drivers/base/core.c:120 device_release()
 [<c0105ff9>] show_trace_log_lvl+0x19/0x2e
 [<c01063e2>] show_trace+0x12/0x14
 [<c01063f8>] dump_stack+0x14/0x16
 [<c063cddf>] device_release+0x7c/0x7e
 [<c0476c32>] kobject_cleanup+0x44/0x5e
 [<c0476c57>] kobject_release+0xb/0xd
 [<c04773ef>] kref_put+0x63/0x71
 [<c0476757>] kobject_put+0x14/0x16
 [<c063ceef>] put_device+0x11/0x13
 [<c063d943>] device_unregister+0x12/0x15
 [<c07337d1>] fixed_mdio_register_device+0x210/0x23b
 [<c1b6d6c1>] fixed_init+0x2f/0x33
 [<c1b31a2d>] init+0x15d/0x2bd
 [<c0105bc3>] kernel_thread_helper+0x7/0x10
 =======================
Calling initcall 0xc1b6d6c5: sundance_init+0x0/0x16()
Calling initcall 0xc1b6d6db: hamachi_init+0x0/0x16()
-
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/