I just upgraded from build 20220101 to 20220121.
I use pam_cifscreds.so but pam-config still does not have built in support for it so for the last 2 years (when I started using TW ) whenever a new build updates pam I have to manually reapply my changes.
I add the following to /etc/pam.d/common-auth
auth optional pam_cifscreds.so
I add the following to /etc/pam.d/common-session
session required pam_keyinit.so
session optional pam_cifscreds.so host=FILESERVER
and then I reboot.
I have 2 mounts in fstab for the cifs shares and they use the multiuser option.
Everything has worked fine for the last 2 years after I reapply the above changes to PAM but after updating to build 20220121, and applying those changes and rebooting when I try to login to the GUI desktop the system either hangs and does not login to the desktop or the login screen is redisplayed after a minute.
If I reboot using the previous kernel I was using (5.15.12-1) with the above pam.d config changes made, then I am able to login without issue and can access the cifs shares without issue so the issue appears to be with the 5.16.1-1 kernel.
If I comment out the pam_keyinit.so line added in common-session and reboot using the 5.16.1-1 kernel then I am able to login to the GUI now.
After logging in I use 'cifscreds -u joe FILESERVER' and enter my password and it completes successfully but when I try to access the cifs mounted share the following entries are in the system journal
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x0000) - not-present page
As mentioned, If I rebooting using the 5.15.12-1 kernel with the 3 above lines added to the pam configs everything works fine.
If I reboot using the 5.15.12-1 kernel but comment out the pam_keyinit.so line (which causes kernel 5.16.1-1 to have the null pointer issue) and then issue the cifscreds command after logging in I am also able to access the cifs shares without issue.
Is this a known issue? Has it been fixed in a TW build after 20220121 ?