Bug 210062
Summary: | possible circular locking dependency detected (kdm and 2.6.18-1.2189.fc5) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | pfrields, wtogami |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-17 20:29:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Orion Poplawski
2006-10-09 19:54:29 UTC
*** Bug 210063 has been marked as a duplicate of this bug. *** A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. Now, it appears that 1.2200.fc5 does not contain the lock dependency validator, as the following lines are missing from dmesg under 1.2200.fc5. I'm assuming that this is what generated the above output and that without it I will not be able to reproduce the above issue. Is that true? < Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar < ... MAX_LOCKDEP_SUBCLASSES: 8 < ... MAX_LOCK_DEPTH: 30 < ... MAX_LOCKDEP_KEYS: 2048 < ... CLASSHASH_SIZE: 1024 < ... MAX_LOCKDEP_ENTRIES: 8192 < ... MAX_LOCKDEP_CHAINS: 8192 < ... CHAINHASH_SIZE: 4096 < memory used by lock dependency info: 696 kB < per task-struct memory footprint: 1200 bytes correct, the validator is disabled in the production kernel. This bug should be fixed regardless, so shouldn't reoccur if it's turned back on at any point. This looks a lot like the same problem again:
Feb 22 12:35:38 apapane kernel: [ INFO: possible circular locking dependency
detected ]
Feb 22 12:35:38 apapane kernel: 2.6.19-1.2911.fc6debug #1
Feb 22 12:35:38 apapane kernel:
-------------------------------------------------------
Feb 22 12:35:38 apapane kernel: sh/4424 is trying to acquire lock:
Feb 22 12:35:38 apapane kernel: (sk_lock-AF_INET){--..}, at:
[<ffffffff8022762d>] tcp_se
ndmsg+0x1c/0xb63
Feb 22 12:35:38 apapane kernel:
Feb 22 12:35:38 apapane kernel: but task is already holding lock:
Feb 22 12:35:38 apapane kernel: (&inode->i_alloc_sem){--..}, at:
[<ffffffff8022e43b>] no
tify_change+0xfd/0x2e1
Feb 22 12:35:38 apapane kernel:
Feb 22 12:35:38 apapane kernel: which lock already depends on the new lock.
Feb 22 12:35:38 apapane kernel:
Feb 22 12:35:38 apapane kernel:
Feb 22 12:35:38 apapane kernel: the existing dependency chain (in reverse order) is:
Feb 22 12:35:38 apapane kernel:
Feb 22 12:35:38 apapane kernel: -> #3 (&inode->i_alloc_sem){--..}:
Feb 22 12:35:38 apapane kernel: [<ffffffff802a5bd4>]
__lock_acquire+0x8bf/0x9d4
Feb 22 12:35:38 apapane kernel: [<ffffffff802a626e>] lock_acquire+0x48/0x63
Feb 22 12:35:38 apapane kernel: [<ffffffff802a20af>] down_write+0x34/0x3d
Feb 22 12:35:38 apapane kernel: [<ffffffff8022e43b>] notify_change+0xfd/0x2e1
Feb 22 12:35:38 apapane kernel: [<ffffffff802dddaf>] do_truncate+0x4e/0x69
Feb 22 12:35:38 apapane kernel: [<ffffffff80212dd0>] may_open+0x1e0/0x252
Feb 22 12:35:38 apapane kernel: [<ffffffff8021beac>] open_namei+0x2cb/0x698
Feb 22 12:35:38 apapane kernel: [<ffffffff80228ea8>] do_filp_open+0x1c/0x38
Feb 22 12:35:38 apapane kernel: [<ffffffff8021a90a>] do_sys_open+0x44/0xbe
Feb 22 12:35:38 apapane kernel: [<ffffffff8025e11e>] system_call+0x7e/0x83
Feb 22 12:35:38 apapane kernel: [<000000000055f5a0>] 0x55f5a0
Feb 22 12:35:38 apapane kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Feb 22 12:35:38 apapane kernel:
Feb 22 12:35:38 apapane kernel: -> #2 (&sysfs_inode_imutex_key){--..}:
Feb 22 12:35:38 apapane kernel: [<ffffffff802a5bd4>]
__lock_acquire+0x8bf/0x9d4
Feb 22 12:35:38 apapane kernel: [<ffffffff802a626e>] lock_acquire+0x48/0x63
Feb 22 12:35:38 apapane kernel: [<ffffffff8026414a>]
__mutex_lock_slowpath+0xed/0x
26f
Feb 22 12:35:38 apapane kernel: [<ffffffff8030b262>] create_dir+0x24/0x1d5
Feb 22 12:35:38 apapane kernel: [<ffffffff8030b823>]
sysfs_create_dir+0x6d/0x8b
Feb 22 12:35:39 apapane kernel: [<ffffffff8034dde2>] kobject_add+0xe2/0x19f
Feb 22 12:35:39 apapane kernel: [<ffffffff803b9d8a>]
class_device_add+0xb2/0x464
Feb 22 12:35:39 apapane kernel: [<ffffffff80421806>]
register_netdevice+0x29a/0x36
8
Feb 22 12:35:39 apapane kernel: [<ffffffff8042192d>]
register_netdev+0x59/0x66
Feb 22 12:35:39 apapane kernel: [<ffffffff8072bdac>]
net_olddevs_init+0xb/0xac
Feb 22 12:35:39 apapane kernel: [<ffffffff8026b71d>] init+0x1e6/0x3ac
Feb 22 12:35:39 apapane kernel: [<ffffffff8025ef48>] child_rip+0xa/0x12
Feb 22 12:35:39 apapane kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Feb 22 12:35:39 apapane kernel:
Feb 22 12:35:39 apapane kernel: -> #1 (rtnl_mutex){--..}:
Feb 22 12:35:39 apapane kernel: [<ffffffff802a5bd4>]
__lock_acquire+0x8bf/0x9d4
Feb 22 12:35:39 apapane kernel: [<ffffffff802a626e>] lock_acquire+0x48/0x63
Feb 22 12:35:39 apapane kernel: [<ffffffff8026414a>]
__mutex_lock_slowpath+0xed/0x
26f
Feb 22 12:35:39 apapane kernel: [<ffffffff80457635>]
ip_mc_leave_group+0x23/0xb8
Feb 22 12:35:39 apapane kernel: [<ffffffff8044193f>]
do_ip_setsockopt+0x6df/0x9cc
Feb 22 12:35:39 apapane kernel: [<ffffffff80441cc6>] ip_setsockopt+0x22/0x78
Feb 22 12:35:39 apapane kernel: [<ffffffff80419039>] sys_setsockopt+0x91/0xb7
Feb 22 12:35:39 apapane kernel: [<ffffffff8025e11e>] system_call+0x7e/0x83
Feb 22 12:35:39 apapane kernel: [<00002aaaabc3a32a>] 0x2aaaabc3a32a
Feb 22 12:35:39 apapane kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Feb 22 12:35:39 apapane kernel:
Feb 22 12:35:39 apapane kernel: -> #0 (sk_lock-AF_INET){--..}:
Feb 22 12:35:39 apapane kernel: [<ffffffff802a5ae8>]
__lock_acquire+0x7d3/0x9d4
Feb 22 12:35:39 apapane kernel: [<ffffffff802a626e>] lock_acquire+0x48/0x63
Feb 22 12:35:39 apapane kernel: [<ffffffff802350ef>] lock_sock+0xd1/0xe1
Feb 22 12:35:39 apapane kernel: [<ffffffff8022762d>] tcp_sendmsg+0x1c/0xb63
Feb 22 12:35:39 apapane kernel: [<ffffffff8025532a>] sock_sendmsg+0xea/0x107
Feb 22 12:35:39 apapane kernel: [<ffffffff80419f28>] kernel_sendmsg+0x2c/0x3e
Feb 22 12:35:39 apapane kernel: [<ffffffff881b76f7>]
xs_tcp_send_request+0x100/0x2
c5 [sunrpc]
Feb 22 12:35:39 apapane kernel: [<ffffffff881b658a>]
xprt_transmit+0xc4/0x1ab [sun
rpc]
Feb 22 12:35:39 apapane kernel: [<ffffffff881b4436>]
call_transmit+0x1f9/0x233 [su
nrpc]
Feb 22 12:35:39 apapane kernel: [<ffffffff881b9bb3>]
__rpc_execute+0xa7/0x1ed [sun
rpc]
Feb 22 12:35:39 apapane kernel: [<ffffffff881b4b0d>]
rpc_call_sync+0x9d/0xca [sunr
pc]
Feb 22 12:35:39 apapane kernel: [<ffffffff88241b39>]
nfs3_rpc_wrapper+0x29/0x6d [n
fs]
Feb 22 12:35:39 apapane kernel: [<ffffffff88241e0a>]
nfs3_proc_setattr+0x97/0xcc [
nfs]
Feb 22 12:35:39 apapane kernel: [<ffffffff88239904>]
nfs_setattr+0xd9/0x10b [nfs]
Feb 22 12:35:39 apapane kernel: [<ffffffff8022e489>]
notify_change+0x14b/0x2e1
Feb 22 12:35:39 apapane kernel: [<ffffffff802dddaf>] do_truncate+0x4e/0x69
Feb 22 12:35:39 apapane kernel: [<ffffffff80212dd0>] may_open+0x1e0/0x252
Feb 22 12:35:39 apapane kernel: [<ffffffff8021beac>] open_namei+0x2cb/0x698
Feb 22 12:35:39 apapane kernel: [<ffffffff80228ea8>] do_filp_open+0x1c/0x38
Feb 22 12:35:39 apapane kernel: [<ffffffff8021a90a>] do_sys_open+0x44/0xbe
Feb 22 12:35:39 apapane kernel: [<ffffffff8025e11e>] system_call+0x7e/0x83
Feb 22 12:35:39 apapane kernel: [<00002aaaab18c480>] 0x2aaaab18c480
Feb 22 12:35:39 apapane kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Feb 22 12:35:39 apapane kernel:
Feb 22 12:35:39 apapane kernel: other info that might help us debug this:
Feb 22 12:35:39 apapane kernel:
Feb 22 12:35:39 apapane kernel: 2 locks held by sh/4424:
Feb 22 12:35:39 apapane kernel: #0: (&inode->i_mutex){--..}, at:
[<ffffffff802ddda4>] d
o_truncate+0x43/0x69
Feb 22 12:35:39 apapane kernel: #1: (&inode->i_alloc_sem){--..}, at:
[<ffffffff8022e43b
>] notify_change+0xfd/0x2e1
Feb 22 12:35:39 apapane kernel:
Feb 22 12:35:39 apapane kernel: stack backtrace:
Feb 22 12:35:39 apapane kernel:
Feb 22 12:35:39 apapane kernel: Call Trace:
Feb 22 12:35:39 apapane kernel: [<ffffffff8026c97e>] show_trace+0x34/0x47
Feb 22 12:35:39 apapane kernel: [<ffffffff8026c9a3>] dump_stack+0x12/0x17
Feb 22 12:35:39 apapane kernel: [<ffffffff802a459f>]
print_circular_bug_tail+0x65/0x6e
Feb 22 12:35:39 apapane kernel: [<ffffffff802a5ae8>] __lock_acquire+0x7d3/0x9d4
Feb 22 12:35:39 apapane kernel: [<ffffffff802a626e>] lock_acquire+0x48/0x63
Feb 22 12:35:39 apapane kernel: [<ffffffff802350ef>] lock_sock+0xd1/0xe1
Feb 22 12:35:39 apapane kernel: [<ffffffff8022762d>] tcp_sendmsg+0x1c/0xb63
Feb 22 12:35:39 apapane kernel: [<ffffffff8025532a>] sock_sendmsg+0xea/0x107
Feb 22 12:35:39 apapane kernel: [<ffffffff80419f28>] kernel_sendmsg+0x2c/0x3e
Feb 22 12:35:39 apapane kernel: [<ffffffff881b76f7>]
:sunrpc:xs_tcp_send_request+0x100/0
x2c5
Feb 22 12:35:39 apapane kernel: [<ffffffff881b658a>]
:sunrpc:xprt_transmit+0xc4/0x1ab
Feb 22 12:35:39 apapane kernel: [<ffffffff881b4436>]
:sunrpc:call_transmit+0x1f9/0x233
Feb 22 12:35:39 apapane kernel: [<ffffffff881b9bb3>]
:sunrpc:__rpc_execute+0xa7/0x1ed
Feb 22 12:35:39 apapane kernel: [<ffffffff881b4b0d>]
:sunrpc:rpc_call_sync+0x9d/0xca
Feb 22 12:35:39 apapane kernel: [<ffffffff88241b39>]
:nfs:nfs3_rpc_wrapper+0x29/0x6d
Feb 22 12:35:39 apapane kernel: [<ffffffff88241e0a>]
:nfs:nfs3_proc_setattr+0x97/0xcc
Feb 22 12:35:39 apapane kernel: [<ffffffff88239904>] :nfs:nfs_setattr+0xd9/0x10b
Feb 22 12:35:39 apapane kernel: [<ffffffff8022e489>] notify_change+0x14b/0x2e1
Feb 22 12:35:39 apapane kernel: [<ffffffff802dddaf>] do_truncate+0x4e/0x69
Feb 22 12:35:39 apapane kernel: [<ffffffff80212dd0>] may_open+0x1e0/0x252
Feb 22 12:35:39 apapane kernel: [<ffffffff8021beac>] open_namei+0x2cb/0x698
Feb 22 12:35:39 apapane kernel: [<ffffffff80228ea8>] do_filp_open+0x1c/0x38
Feb 22 12:35:39 apapane kernel: [<ffffffff8021a90a>] do_sys_open+0x44/0xbe
Feb 22 12:35:39 apapane kernel: [<ffffffff8025e11e>] system_call+0x7e/0x83
Feb 22 12:35:39 apapane kernel: [<00002aaaab18c480>]
Feb 22 12:35:39 apapane kernel:
|