Description of problem: Visiting cifs shares causes system to freeze. kernel-6.0.16-300.fc37.x86_64 cifs-utils-6.15-2.fc37.x86_64 How reproducible: Everytime while booted to 6.0.16 kernel. Reverting to kernel-6.0.15 there are no issues visiting mounted shares. Steps to Reproduce: After update to the noted kernel above. These steps were conducted in console (tty2) so that error output would be revealed. sudo mount.cifs -o username=jbk,uid=jbk,gid=jbk //bagend/bits ~/bits Password for jbk@//bagend/bits: After mount visiting any share bits]$ cd <share> causes the machine to freeze. Additional info: Link to fedora forum thread. See post #12 for screen shot of crash output. https://forums.fedoraforum.org/showthread.php?329684-mounts-no-longer-working&p=1865088#post1865088 This issue has been reported on the forum by multiple users.
Can confirm this. cd or ls freeze the system. Happens on two different devices. No problems with the last kernel.
This bug has been reported also on kernel org [bugzilla.kernel.org/show_bug.cgi?id=216895] A patch has been incorporated in 6.0.18 kernel in testing.
Moving to kernel package. cifs-utils is a user space one that does not implement the SMB protocol but rather helps to establish the session. The bug is in the kernel side of things.
facing the same issue on a clean install today, good to know it's fixed in the latest kernel
6.0.18-200 does not appear to have fixed this. On boot to that kernel, with cifs mounts enabled in fstab, system will boot to DE login but on attempt to login, kernel freezes. To test, I comment out cifs mount entries in fstab and system / DE load as expected. Last know kernel where these issues _do-not_ happen is 6.0.15-200 Note: this is on f36 w/Cinnamon CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (1.60GHz, VGA: NVIDIA Corporation GF108 [GeForce GT 730], 32Gb memory.
*** Bug 2159059 has been marked as a duplicate of this bug. ***
Installation of the 6.0.18-300.fc37.x86_64 kernel from the updates repo has resolved the issue for me.
Confirming that installation of the 6.0.18-300.fc37.x86_64 kernel worked for me as well. Thanks to everyone involved in resolving this!
Also confirming that upgrade from f36 to f37 w/ kernel 6.0.18-300 resolves this issue. Many thanks.