Bug 928542

Summary: [abrt] [ BUG: mount.nfs/2458 still has locks held! ]
Product: [Fedora] Fedora Reporter: Chuck Forsberg <caf>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jlayton, jonathan, kernel-maint, madhu.chinakonda, PTrenholme, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:02b34c9d0e14548d7a067a865617da73af5b6261
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-08 19:24:38 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:
Attachments:
Description Flags
File: dmesg none

Description Chuck Forsberg 2013-03-27 21:07:58 UTC
Additional info:
[ BUG: mount.nfs/2458 still has locks held! ]
3.9.0-0.rc4.git0.1.fc19.x86_64 #1 Not tainted
-------------------------------------
1 lock held by mount.nfs/2458:
 #0:  (nfs_clid_init_mutex){+.+...}, at: [<ffffffffa0740b34>] nfs4_discover_server_trunking+0x94/0x2b0 [nfsv4]
stack backtrace:
Pid: 2458, comm: mount.nfs Not tainted 3.9.0-0.rc4.git0.1.fc19.x86_64 #1
Call Trace:
 [<ffffffff810d6c02>] debug_check_no_locks_held+0x92/0xa0
 [<ffffffffa0677435>] rpc_wait_bit_killable+0x85/0xb0 [sunrpc]
 [<ffffffff81719050>] __wait_on_bit+0x60/0x90
 [<ffffffffa06773b0>] ? __rpc_wait_for_completion_task+0x30/0x30 [sunrpc]
 [<ffffffffa066bc70>] ? call_connect+0x90/0x90 [sunrpc]
 [<ffffffff817190f7>] out_of_line_wait_on_bit+0x77/0x90
 [<ffffffff81095b90>] ? autoremove_wake_function+0x40/0x40
 [<ffffffff81071f89>] ? local_bh_enable_ip+0x89/0xf0
 [<ffffffffa066bc70>] ? call_connect+0x90/0x90 [sunrpc]
 [<ffffffffa0678989>] __rpc_execute+0x189/0x590 [sunrpc]
 [<ffffffff81095b45>] ? wake_up_bit+0x25/0x30
 [<ffffffffa0679915>] rpc_execute+0x55/0x160 [sunrpc]
 [<ffffffffa066fa80>] rpc_run_task+0x70/0x90 [sunrpc]
 [<ffffffffa066fae3>] rpc_call_sync+0x43/0xa0 [sunrpc]
 [<ffffffffa07308c7>] nfs4_proc_setclientid+0x1f7/0x440 [nfsv4]
 [<ffffffffa07307bf>] ? nfs4_proc_setclientid+0xef/0x440 [nfsv4]
 [<ffffffffa073df6f>] nfs40_discover_server_trunking+0x13f/0x2b0 [nfsv4]
 [<ffffffffa073de35>] ? nfs40_discover_server_trunking+0x5/0x2b0 [nfsv4]
 [<ffffffffa0740b5d>] nfs4_discover_server_trunking+0xbd/0x2b0 [nfsv4]
 [<ffffffffa074a61c>] nfs4_init_client+0x11c/0x310 [nfsv4]
 [<ffffffff81021cf5>] ? native_sched_clock+0x15/0x80
 [<ffffffff81021d69>] ? sched_clock+0x9/0x10
 [<ffffffff810acdd5>] ? sched_clock_cpu+0xb5/0x100
 [<ffffffff810d518d>] ? trace_hardirqs_off+0xd/0x10
 [<ffffffff810acf0f>] ? local_clock+0x5f/0x70
 [<ffffffff810d5def>] ? lock_release_holdtime.part.28+0xf/0x190
 [<ffffffffa06edfb6>] nfs_get_client+0x486/0x640 [nfs]
 [<ffffffffa06edc70>] ? nfs_get_client+0x140/0x640 [nfs]
 [<ffffffffa074a018>] nfs4_set_client.isra.8+0x78/0x100 [nfsv4]
 [<ffffffffa074b9c3>] nfs4_create_server+0xf3/0x3a0 [nfsv4]
 [<ffffffffa07414be>] nfs4_remote_mount+0x2e/0x60 [nfsv4]
 [<ffffffff811ded79>] mount_fs+0x39/0x1b0
 [<ffffffff81188e70>] ? __alloc_percpu+0x10/0x20
 [<ffffffff811fc9c3>] vfs_kern_mount+0x63/0xf0
 [<ffffffffa0741396>] nfs_do_root_mount+0x86/0xc0 [nfsv4]
 [<ffffffffa07417b4>] nfs4_try_mount+0x44/0xc0 [nfsv4]
 [<ffffffffa06eed37>] ? get_nfs_version+0x27/0x80 [nfs]
 [<ffffffffa06f9c05>] nfs_fs_mount+0x5c5/0xd10 [nfs]
 [<ffffffffa06fa5d0>] ? nfs_clone_super+0x140/0x140 [nfs]
 [<ffffffffa06f7f90>] ? param_set_portnr+0x60/0x60 [nfs]
 [<ffffffff811ded79>] mount_fs+0x39/0x1b0
 [<ffffffff81188e70>] ? __alloc_percpu+0x10/0x20
 [<ffffffff811fc9c3>] vfs_kern_mount+0x63/0xf0
 [<ffffffff811ff0bd>] do_mount+0x1fd/0xa10
 [<ffffffff811ff953>] sys_mount+0x83/0xc0
 [<ffffffff81727319>] system_call_fastpath+0x16/0x1b

Potential duplicate: bug 917164

Comment 1 Chuck Forsberg 2013-03-27 21:08:03 UTC
Created attachment 717299 [details]
File: dmesg

Comment 2 Jeff Layton 2013-05-08 19:24:38 UTC
The patch that caused that has been backed out of 3.9, and is being reworked upstream not to cause the warning to pop. Fixing the actual problem that it's warning about is a much larger project and will take a while.

I'll go ahead and close this as being resolved upstream for now.

Comment 3 Jeff Layton 2013-05-08 19:28:19 UTC
*** Bug 924380 has been marked as a duplicate of this bug. ***