| 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
| ||
|
Date: Mon, 23 Feb 2009 14:17:12 +0530
From: "Sachin P. Sant" <sachinp@...ibm.com>
To: linuxppc-dev@...abs.org, netdev <netdev@...r.kernel.org>
CC: TKLEIN@...ibm.com, Jan-Bernd Themann <THEMANN@...ibm.com>,
Mel Gorman <mel@....ul.ie>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Subject: [Powerpc / eHEA] Circular dependency with 2.6.29-rc6
While booting 2.6.29-rc6 on a powerpc box came across this
circular dependency with eHEA driver.
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.29-rc6 #2
-------------------------------------------------------
ip/2174 is trying to acquire lock:
(&ehea_fw_handles.lock){--..}, at: [<d000000002a13e30>] .ehea_up+0x64/0x6e0
[ehea]
but task is already holding lock:
(&port->port_lock){--..}, at: [<d000000002a1533c>] .ehea_open+0x3c/0xc4 [ehea]
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&port->port_lock){--..}:
[<c0000000000a8590>] .__lock_acquire+0x7e0/0x8a8
[<c0000000000a86ac>] .lock_acquire+0x54/0x80
[<c0000000005d7564>] .mutex_lock_nested+0x190/0x46c
[<d000000002a1533c>] .ehea_open+0x3c/0xc4 [ehea]
[<c000000000537834>] .dev_open+0xf4/0x168
[<c000000000535780>] .dev_change_flags+0xe4/0x1e8
[<c000000000597bfc>] .devinet_ioctl+0x2c4/0x750
[<c0000000005997a8>] .inet_ioctl+0xcc/0x11c
[<c000000000523400>] .sock_ioctl+0x2f0/0x34c
[<c0000000001380ec>] .vfs_ioctl+0x5c/0xf0
[<c000000000138810>] .do_vfs_ioctl+0x690/0x70c
[<c000000000138900>] .SyS_ioctl+0x74/0xb8
[<c00000000016fb08>] .dev_ifsioc+0x210/0x4b8
[<c00000000016ef18>] .compat_sys_ioctl+0x3f4/0x488
[<c00000000000855c>] syscall_exit+0x0/0x40
-> #1 (rtnl_mutex){--..}:
[<c0000000000a8590>] .__lock_acquire+0x7e0/0x8a8
[<c0000000000a86ac>] .lock_acquire+0x54/0x80
[<c0000000005d7564>] .mutex_lock_nested+0x190/0x46c
[<c0000000005430a8>] .rtnl_lock+0x20/0x38
[<c00000000053677c>] .register_netdev+0x1c/0x80
[<d000000002a12714>] .ehea_setup_single_port+0x2c8/0x3d0 [ehea]
[<d000000002a19da8>] .ehea_probe_adapter+0x288/0x394 [ehea]
[<c00000000051f034>] .of_platform_device_probe+0x78/0x86c
[<c00000000047faec>] .driver_probe_device+0x13c/0x200
[<c00000000047fc44>] .__driver_attach+0x94/0xd8
[<c00000000047eab4>] .bus_for_each_dev+0x80/0xd8
[<c00000000047f850>] .driver_attach+0x28/0x40
[<c00000000047f23c>] .bus_add_driver+0xd4/0x284
[<c00000000047ff7c>] .driver_register+0xc4/0x198
[<c00000000051eeec>] .of_register_driver+0x4c/0x60
[<c000000000024da4>] .ibmebus_register_driver+0x30/0x4c
[<d000000002a1a090>] .ehea_module_init+0x1dc/0x234c [ehea]
[<c000000000009368>] .do_one_initcall+0x90/0x1b0
[<c0000000000b2f24>] .SyS_init_module+0xc8/0x220
[<c00000000000855c>] syscall_exit+0x0/0x40
-> #0 (&ehea_fw_handles.lock){--..}:
[<c0000000000a8590>] .__lock_acquire+0x7e0/0x8a8
[<c0000000000a86ac>] .lock_acquire+0x54/0x80
[<c0000000005d7564>] .mutex_lock_nested+0x190/0x46c
[<d000000002a13e30>] .ehea_up+0x64/0x6e0 [ehea]
[<d000000002a15364>] .ehea_open+0x64/0xc4 [ehea]
[<c000000000537834>] .dev_open+0xf4/0x168
[<c000000000535780>] .dev_change_flags+0xe4/0x1e8
[<c000000000597bfc>] .devinet_ioctl+0x2c4/0x750
[<c0000000005997a8>] .inet_ioctl+0xcc/0x11c
[<c000000000523400>] .sock_ioctl+0x2f0/0x34c
[<c0000000001380ec>] .vfs_ioctl+0x5c/0xf0
[<c000000000138810>] .do_vfs_ioctl+0x690/0x70c
[<c000000000138900>] .SyS_ioctl+0x74/0xb8
[<c00000000016fb08>] .dev_ifsioc+0x210/0x4b8
[<c00000000016ef18>] .compat_sys_ioctl+0x3f4/0x488
[<c00000000000855c>] syscall_exit+0x0/0x40
other info that might help us debug this:
2 locks held by ip/2174:
#0: (rtnl_mutex){--..}, at: [<c0000000005430a8>] .rtnl_lock+0x20/0x38
#1: (&port->port_lock){--..}, at: [<d000000002a1533c>] .ehea_open+0x3c/0xc4
[ehea]
stack backtrace:
Call Trace:
[c00000004246b070] [c00000000001154c] .show_stack+0x70/0x184 (unreliable)
[c00000004246b120] [c0000000000a6ee4] .print_circular_bug_tail+0xd8/0xfc
[c00000004246b1f0] [c0000000000a76ec] .validate_chain+0x7e4/0xea8
[c00000004246b2b0] [c0000000000a8590] .__lock_acquire+0x7e0/0x8a8
[c00000004246b3a0] [c0000000000a86ac] .lock_acquire+0x54/0x80
[c00000004246b430] [c0000000005d7564] .mutex_lock_nested+0x190/0x46c
[c00000004246b510] [d000000002a13e30] .ehea_up+0x64/0x6e0 [ehea]
[c00000004246b610] [d000000002a15364] .ehea_open+0x64/0xc4 [ehea]
[c00000004246b6b0] [c000000000537834] .dev_open+0xf4/0x168
[c00000004246b740] [c000000000535780] .dev_change_flags+0xe4/0x1e8
[c00000004246b7f0] [c000000000597bfc] .devinet_ioctl+0x2c4/0x750
[c00000004246b8f0] [c0000000005997a8] .inet_ioctl+0xcc/0x11c
[c00000004246b960] [c000000000523400] .sock_ioctl+0x2f0/0x34c
[c00000004246ba00] [c0000000001380ec] .vfs_ioctl+0x5c/0xf0
[c00000004246baa0] [c000000000138810] .do_vfs_ioctl+0x690/0x70c
[c00000004246bb80] [c000000000138900] .SyS_ioctl+0x74/0xb8
[c00000004246bc30] [c00000000016fb08] .dev_ifsioc+0x210/0x4b8
[c00000004246bd40] [c00000000016ef18] .compat_sys_ioctl+0x3f4/0x488
[c00000004246be30] [c00000000000855c] syscall_exit+0x0/0x40
ehea: eth2: Physical port up
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists