[elrepo] CIFS issue with kernel-ml 4.10.4-1

[Weiner, Michael]

I have been looking through the archives and bugs and have not seen anyone writing about this in the recent history, so I am writing to the  list to see if anyone can help. I manage a CentOS 6.8 server for some computing work here, and an end-user needs to get data she is working with from her CIFS mounted lab share. I wrote her a little script so she can mount this herself:

#!/bin/bash
sudo mount -t cifs //smb-isi1.lerner.ccf.org/padgetrlab ~/padgetrlab -o username=hershbc,password=*********,domain=LERNER,uid=1528,gid=196

and that works fine, however recently we have been experiencing some 'freezes' when doing a df or an ls, and the load average when this occurs is extremely high (<80). I see this in the kernel messages:

INFO: task bedtools:4705 blocked for more than 120 seconds.
      Not tainted 2.6.32-642.6.2.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
bedtools      D 0000000000000001     0  4705      1 0x00000084
 ffff88081925b9e8 0000000000000046 ffff88201ad98940 0000000000002710
 0000000000000000 0000002f19706400 ffff88194fbdbd70 ffff880800000019
 ffff8800232cb280 ffff880800000015 ffff88081b9d85f8 ffff88081925bfd8
Call Trace:
 [<ffffffff8112e3f0>] ? sync_page+0x0/0x50
 [<ffffffff815491c3>] io_schedule+0x73/0xc0
 [<ffffffff8112e42d>] sync_page+0x3d/0x50
 [<ffffffff81549caf>] __wait_on_bit+0x5f/0x90
 [<ffffffff8112e663>] wait_on_page_bit+0x73/0x80
 [<ffffffff810a6920>] ? wake_bit_function+0x0/0x50
 [<ffffffff811447a5>] ? pagevec_lookup_tag+0x25/0x40
 [<ffffffff8112ea8b>] wait_on_page_writeback_range+0xfb/0x190
 [<ffffffff8112eb4f>] filemap_fdatawait+0x2f/0x40
 [<ffffffff8112f174>] filemap_write_and_wait+0x44/0x60
 [<ffffffffa0703295>] cifs_flush+0x55/0x80 [cifs]
 [<ffffffff8119683c>] filp_close+0x3c/0x90
 [<ffffffff8107f74f>] put_files_struct+0x7f/0xf0
 [<ffffffff8107f813>] exit_files+0x53/0x70
 [<ffffffff810818bd>] do_exit+0x18d/0x870
 [<ffffffff81199870>] ? do_sync_write+0x0/0x140
 [<ffffffff81081ff8>] do_group_exit+0x58/0xd0
 [<ffffffff81097e06>] get_signal_to_deliver+0x1f6/0x460
 [<ffffffffa06ed107>] ? cifs_file_aio_write+0x27/0x80 [cifs]
 [<ffffffff8100a285>] do_signal+0x75/0x870
 [<ffffffff81199ce2>] ? vfs_write+0x132/0x1a0
 [<ffffffff8100ab10>] do_notify_resume+0x90/0xc0
 [<ffffffff8100b3a1>] int_signal+0x12/0x17

It isn't a problem with bedtools per se, but that was the tool that the end-user was using against some data that resides in her lab share on this CIFS mount on the server, so technically it could be any process really that hits the share. So after a heck of a lot of digging into a lot of useless nothing on the internet, I found a potential answer. The answer could potentially lie in the fact that CIFS module in the standard OS kernel was very old and had never been patched against this bug (std kernel for CentOS 6.8 is kernel-2.6.32-642.6.2.el6.x86_64), so the suggestion was to enable an enterprise linux repository that has newer builds of the mainline kernel (in this case kernel- 4.10.6-1.el6.elrepo.x86_64) that has a newer and patched version of the CIFS module. So it was pretty easy to enable and install the kernel (with little or no impact on the OS) for some testing by the end user. However the problem is now, that when the end user runs her mount script it fails, with a permission denied and throws this in the kernel messages:

Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13

So now, we are unable to mount the CIFS share at all. Has anyone else seen this and how do I overcome this issue. 

Regards
Michael Weiner

===================================


 Please consider the environment before printing this e-mail

Cleveland Clinic is ranked as one of the top hospitals in America by U.S.News & World Report (2015).  
Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations.


Confidentiality Note:  This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law.  If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error,  please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.  

Thank you.