Description of problem:
CIFS response on my system(s) can be VERY slow. All the CIFS shares are listed in /etc/fstab with the options "_netdev,nofail," so, theoretically, the presence of the locks should not be a problem that would, or should, cause an "oops" in the kernel.

Note that this is NOT a fatal problem. I don't know why it gets raised to the level of a "kerneloops."

Additional info:
[ BUG: mount.cifs/713 still has locks held! ]
3.9.0-0.rc3.git0.4.fc19.x86_64 #1 Not tainted
-------------------------------------
1 lock held by mount.cifs/713:
 #0:  (&ret_buf->session_mutex){+.+...}, at: [<ffffffffa0666bf3>] cifs_get_smb_ses+0x153/0x4b0 [cifs]
stack backtrace:
Pid: 713, comm: mount.cifs Not tainted 3.9.0-0.rc3.git0.4.fc19.x86_64 #1
Call Trace:
 [<ffffffff810d6c02>] debug_check_no_locks_held+0x92/0xa0
 [<ffffffffa0678fd5>] wait_for_response.isra.6+0xa5/0x150 [cifs]
 [<ffffffff81095b70>] ? wake_up_bit+0x30/0x30
 [<ffffffffa0679fc6>] SendReceive+0x146/0x310 [cifs]
 [<ffffffffa0657422>] CIFSSMBNegotiate+0x132/0x920 [cifs]
 [<ffffffffa0681667>] cifs_negotiate+0x17/0x60 [cifs]
 [<ffffffffa0666847>] cifs_negotiate_protocol+0x77/0xd0 [cifs]
 [<ffffffffa0666bfe>] cifs_get_smb_ses+0x15e/0x4b0 [cifs]
 [<ffffffffa0667086>] cifs_mount+0x136/0xb70 [cifs]
 [<ffffffffa0655fec>] cifs_do_mount+0xac/0x4f0 [cifs]
 [<ffffffff811dec79>] mount_fs+0x39/0x1b0
 [<ffffffff811fc8c3>] vfs_kern_mount+0x63/0xf0
 [<ffffffff811fefbd>] do_mount+0x1fd/0xa10
 [<ffffffff811fec46>] ? copy_mount_options+0x36/0x170
 [<ffffffff811ff853>] sys_mount+0x83/0xc0
 [<ffffffff81726a19>] system_call_fastpath+0x16/0x1b