Re: more rc1 lockdep fun.

2006-07-07 Thread Arjan van de Ven
On Fri, 2006-07-07 at 14:58 -0400, Dave Jones wrote:
 ===
 [ INFO: possible circular locking dependency detected ]
 ---
 gnome-settings-/3278 is trying to acquire lock:
  (sk_lock-AF_INET){--..}, at: [8022800c] tcp_sendmsg+0x1f/0xb1a


this appears to be the same one as the mc one I just looked at.


-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


more rc1 lockdep fun.

2006-07-07 Thread Dave Jones
===
[ INFO: possible circular locking dependency detected ]
---
gnome-settings-/3278 is trying to acquire lock:
 (sk_lock-AF_INET){--..}, at: [8022800c] tcp_sendmsg+0x1f/0xb1a

but task is already holding lock:
 (inode-i_mutex){--..}, at: [802692e0] mutex_lock+0x2a/0x2e

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

- #2 (inode-i_mutex){--..}:
   [802ab6d5] lock_acquire+0x4a/0x69
   [80269102] __mutex_lock_slowpath+0xeb/0x29f
   [802692df] mutex_lock+0x29/0x2e
   [8030f4a0] create_dir+0x2c/0x1e2
   [8030fa5b] sysfs_create_dir+0x59/0x78
   [8034d2e2] kobject_add+0x114/0x1d8
   [803bb1e7] class_device_add+0xb5/0x49d
   [804300b1] netdev_register_sysfs+0x98/0xa2
   [80426f58] register_netdevice+0x28c/0x376
   [8042709c] register_netdev+0x5a/0x69
   [8098aa12] loopback_init+0x4e/0x53
   [8098a918] net_olddevs_init+0xb/0xb7
   [80270918] init+0x177/0x348
   [80263cdd] child_rip+0x7/0x12

- #1 (rtnl_mutex){--..}:
   [802ab6d5] lock_acquire+0x4a/0x69
   [80269102] __mutex_lock_slowpath+0xeb/0x29f
   [802692df] mutex_lock+0x29/0x2e
   [8042e0a2] rtnl_lock+0xf/0x12
   [8045c7b8] ip_mc_leave_group+0x1e/0xae
   [804467f7] do_ip_setsockopt+0x6ad/0x9b2
   [80446baa] ip_setsockopt+0x2a/0x84
   [80454a55] udp_setsockopt+0xd/0x1c
   [8041f7ea] sock_common_setsockopt+0xe/0x11
   [8041e965] sys_setsockopt+0x8e/0xb4
   [80262f19] tracesys+0xd0/0xdb

- #0 (sk_lock-AF_INET){--..}:
   [802ab6d5] lock_acquire+0x4a/0x69
   [802371ea] lock_sock+0xd4/0xe7
   [8022800b] tcp_sendmsg+0x1e/0xb1a
   [80248f4b] inet_sendmsg+0x45/0x53
   [80259d25] sock_sendmsg+0x110/0x130
   [8041f462] kernel_sendmsg+0x3c/0x52
   [885359e9] xs_tcp_send_request+0x117/0x320 [sunrpc]
   [885348d5] xprt_transmit+0x105/0x21e [sunrpc]
   [8853371e] call_transmit+0x1f4/0x239 [sunrpc]
   [8853806e] __rpc_execute+0x9b/0x1e6 [sunrpc]
   [885381de] rpc_execute+0x1a/0x1d [sunrpc]
   [885324ad] rpc_call_sync+0x87/0xb9 [sunrpc]
   [8859e587] nfs3_rpc_wrapper+0x2e/0x74 [nfs]
   [8859ea14] nfs3_proc_lookup+0xe0/0x163 [nfs]
   [88590b10] nfs_lookup+0xef/0x1d6 [nfs]
   [8020d300] do_lookup+0xd0/0x18c
   [802098b6] __link_path_walk+0x3b8/0xf7d
   [8020f076] link_path_walk+0x69/0x101
   [8020d096] do_path_lookup+0x27b/0x2e7
   [802258da] __user_walk_fd+0x40/0x5c
   [802360f7] sys_faccessat+0xf3/0x1aa
   [802e08a5] sys_access+0x12/0x15
   [80262f19] tracesys+0xd0/0xdb

other info that might help us debug this:

1 lock held by gnome-settings-/3278:
 #0:  (inode-i_mutex){--..}, at: [802692e0] mutex_lock+0x2a/0x2e

stack backtrace:

Call Trace:
 [80271910] show_trace+0xaa/0x23d
 [80271ab8] dump_stack+0x15/0x17
 [802a992f] print_circular_bug_tail+0x6c/0x77
 [802aaf34] __lock_acquire+0x853/0xa54
 [802ab6d6] lock_acquire+0x4b/0x69
 [802371eb] lock_sock+0xd5/0xe7
 [8022800c] tcp_sendmsg+0x1f/0xb1a
 [80248f4c] inet_sendmsg+0x46/0x53
 [80259d26] sock_sendmsg+0x111/0x130
 [8041f463] kernel_sendmsg+0x3d/0x52
 [885359ea] :sunrpc:xs_tcp_send_request+0x118/0x320
 [885348d6] :sunrpc:xprt_transmit+0x106/0x21e
 [8853371f] :sunrpc:call_transmit+0x1f5/0x239
 [8853806f] :sunrpc:__rpc_execute+0x9c/0x1e6
 [885381df] :sunrpc:rpc_execute+0x1b/0x1d
 [885324ae] :sunrpc:rpc_call_sync+0x88/0xb9
 [8859e588] :nfs:nfs3_rpc_wrapper+0x2f/0x74
 [8859ea15] :nfs:nfs3_proc_lookup+0xe1/0x163
 [88590b11] :nfs:nfs_lookup+0xf0/0x1d6
 [8020d301] do_lookup+0xd1/0x18c
 [802098b7] __link_path_walk+0x3b9/0xf7d
 [8020f077] link_path_walk+0x6a/0x101
 [8020d097] do_path_lookup+0x27c/0x2e7
 [802258db] __user_walk_fd+0x41/0x5c
 [802360f8] sys_faccessat+0xf4/0x1aa
 [802e08a6] sys_access+0x13/0x15
 [80262f1a] tracesys+0xd1/0xdb

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: more rc1 lockdep fun.

2006-07-07 Thread David Miller
From: Arjan van de Ven [EMAIL PROTECTED]
Date: Fri, 07 Jul 2006 21:03:35 +0200

 On Fri, 2006-07-07 at 14:58 -0400, Dave Jones wrote:
  ===
  [ INFO: possible circular locking dependency detected ]
  ---
  gnome-settings-/3278 is trying to acquire lock:
   (sk_lock-AF_INET){--..}, at: [8022800c] tcp_sendmsg+0x1f/0xb1a
 
 
 this appears to be the same one as the mc one I just looked at.

This is what I think too, I'll look at Arjan's analysis later this
afternoon.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html