regression in CIFS(?) between 4.17.14 and 4.18.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Apologies in advance for not having a better troubleshooting approach.
I'm at a loss...

I maintain a large number of CentOS 7 based machines that utilize
pam_mount to service (CIFS) user homedirs. This has worked swimmingly
for many years. I recently rebooted a test node into both kernels
4.18.0 and 4.18.1 to find that upon user login (the triggering of
pam_mount of CIFS homedir -- eg, local users/homedirs do not trip the
problem), the kernel spontaneously reboots :/ Roll back to 4.17.4 and
all is well again. Further strang-ifying things, is that static CIFS
mounts (via /etc/fstab) _do_ mount as expected in 4.18.x.

functional state:

$ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)

$ uname -r
4.17.14-1.el7.elrepo.x86_64

$ rpm -qa |grep pam_mount
pam_mount-2.16-5.el7.x86_64

$ grep "$(whoami)" /proc/mounts
//dfs.ad.domain/path/to/USER /home/ad.domain/USER cifs
rw,relatime,vers=2.0,sec=krb5i,cache=strict,username=user,domain=ad.domain,uid=MYUID,forceuid,gid=MYGID,forcegid,addr=dfs.target.ip,file_mode=0700,dir_mode=0700,soft,nounix,serverino,mapposix,rsize=65536,wsize=65536,echo_interval=60,actimeo=1
0 0


Given that the static mounts (which use ntlmsspi) work fine (in
4.18.x) i, I thought I'd return the user homes back to ntlmsspi; but
the spontaneous reboot is still triggered.

Any ideas how I might better troubleshoot this? Or is this possibly
pam_mount somehow tickling the newer kernels in a bad way?

Thanks in advance



[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux