15.4 kernel 5.14.21-150400.24.38-default not usable on OS/2 LAN
5.14.21-150400.24.38-default boots, but I can't use it, because OS/2 connectivity is a must. 5.14.21-150400.24.33-default solves the problem, keeps OS/2 connected. What changed this time? The vers=1.0 hit in the error message doesn't seem could apply, since it's already being used: /etc/fstab includes: //os2/G /smbmnt/os2/G cifs ro,credentials=/etc/samba/os2.cred,noserverino,sec=lanman,vers=1.0,servern=OS2,domain=PEERS,port=139,dir_mode=0555,file_mode=0664,noauto 0 0 # alias | grep mountos2 alias mountos2='mount //os2/G' # mountos2 mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) With the older kernel and working as expected, the journal contained the following: ## kernel 24.33 - OK # journalctl -b | grep -i -C3 cifs > Jan 01 03:47:59 at-spi-bus-launcher[1378]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jan 01 03:48:06 kernel: FS-Cache: Loaded Jan 01 03:48:06 kernel: Key type dns_resolver registered Jan 01 03:48:06 kernel: FS-Cache: Netfs 'cifs' registered for caching Jan 01 03:48:06 kernel: Key type cifs.spnego registered Jan 01 03:48:06 kernel: Key type cifs.idmap registered Jan 01 03:48:06 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: Attempting to mount \\mazda\E Jan 01 03:48:06 kernel: CIFS: VFS: Send error in QFSAttributeInfo = -95 Jan 01 03:48:06 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: Attempting to mount \\mazda\G Jan 01 03:48:06 kernel: CIFS: VFS: Send error in QFSAttributeInfo = -95 Jan 01 03:48:06 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: Attempting to mount \\mazda\I Jan 01 03:48:06 kernel: CIFS: VFS: Send error in QFSAttributeInfo = -95 Jan 01 03:48:06 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:48:06 kernel: CIFS: Attempting to mount \\mazda\J Jan 01 03:48:06 kernel: CIFS: VFS: Send error in QFSAttributeInfo = -95 ... Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:54:04 kernel: CIFS: VFS: Invalid date, month 0 day: 0 Jan 01 03:58:04 kernel: CIFS: VFS: bogus file nlink value 0 Jan 01 03:58:04 kernel: CIFS: VFS: bogus file nlink value 0 ... Jan 01 04:18:25 kernel: CIFS: VFS: bogus file nlink value 0 Jan 01 04:18:25 kernel: CIFS: VFS: bogus file nlink value 0 With the 5.14.21-150400.24.38 kernel, I get the following excerpts instead from a full journal at https://susepaste.org/29524759 : Jan 01 03:23:52 kernel: CIFS: Attempting to mount \\os2\E Jan 01 03:23:52 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:23:52 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:23:52 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:23:52 kernel: CIFS: Attempting to mount \\os2\G Jan 01 03:23:52 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:23:52 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:23:52 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:23:52 kernel: CIFS: Attempting to mount \\os2\I Jan 01 03:23:53 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:23:53 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:23:53 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:23:53 kernel: CIFS: Attempting to mount \\os2\J Jan 01 03:23:53 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:36:00 systemd[1]: Starting Cleanup of Temporary Directories... Jan 01 03:36:00 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jan 01 03:36:00 systemd[1]: Finished Cleanup of Temporary Directories. Jan 01 03:37:57 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:37:57 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:37:57 kernel: CIFS: Attempting to mount \\os2\E Jan 01 03:37:58 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:37:58 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:37:58 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:37:58 kernel: CIFS: Attempting to mount \\os2\G Jan 01 03:37:58 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:37:58 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:37:58 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:37:58 kernel: CIFS: Attempting to mount \\os2\I Jan 01 03:37:59 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:38:13 systemd-logind[843]: New session 3 of user root. Jan 01 03:38:13 systemd[1]: Started Session 3 of User root. Jan 01 03:38:13 kdm[1021]: :0[1021]: pam_unix(xdm:session): session opened for user root by (uid=0) -- Jan 01 03:38:16 at-spi-bus-launcher[1499]: dbus-daemon[1499]: Successfully activated service 'org.a11y.atspi.Registry' Jan 01 03:38:16 at-spi-bus-launcher[1516]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jan 01 03:38:37 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:37 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:37 kernel: CIFS: Attempting to mount \\os2\E Jan 01 03:38:38 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:38:38 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:38 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:38 kernel: CIFS: Attempting to mount \\os2\G Jan 01 03:38:38 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:38:38 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:38 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:38 kernel: CIFS: Attempting to mount \\os2\I Jan 01 03:38:39 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:38:39 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:39 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jan 01 03:38:39 kernel: CIFS: Attempting to mount \\os2\J Jan 01 03:38:39 kernel: CIFS: VFS: cifs_mount failed w/return code = -112 Jan 01 03:46:41 kdm[1021]: :0[1021]: pam_unix(xdm:session): session closed for user root Jan 01 03:46:41 at-spi-bus-launcher[1516]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Jan 01 03:46:41 at-spi-bus-launcher[1516]: after 157 requests (157 known processed) with 0 events remaining. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 02.01.23 05:43, Felix Miata wrote:
5.14.21-150400.24.38-default boots, but I can't use it, because OS/2 connectivity is a must. 5.14.21-150400.24.33-default solves the problem, keeps OS/2 connected. [...] mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
I also observe a regression with openSUSE Leap 15.4 (x86-64) for SMB mounts between these two kernels: ok kernel-default-5.14.21-150400.24.33.2.x86_64 FAIL kernel-default-5.14.21-150400.24.38.1.x86_64 Failing SMB shares are configured with CIFS version 1.0. (I know, you're not supposed to use 1.0, but I'm not calling the shots on that one.) Error reported by mount is different, though: - Exit code 32 - Return code 20 (not a directory) I haven't found a bugzilla entry on b.o.o. Regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024
On 02.01.23 16:41, Till Dörges wrote:
On 02.01.23 05:43, Felix Miata wrote:
5.14.21-150400.24.38-default boots, but I can't use it, because OS/2 connectivity is a must. 5.14.21-150400.24.33-default solves the problem, keeps OS/2 connected. [...] mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
I also observe a regression with openSUSE Leap 15.4 (x86-64) for SMB mounts between these two kernels:
ok kernel-default-5.14.21-150400.24.33.2.x86_64 FAIL kernel-default-5.14.21-150400.24.38.1.x86_64
Failing SMB shares are configured with CIFS version 1.0. (I know, you're not supposed to use 1.0, but I'm not calling the shots on that one.)
Error reported by mount is different, though:
- Exit code 32 - Return code 20 (not a directory)
The share in question is configured with CIFS version 1.0 and security mode NTLM.
I haven't found a bugzilla entry on b.o.o.
Upstream apparently has gotten rid of NTLM already: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... Also this upstream bug seems to be related: https://bugzilla.kernel.org/show_bug.cgi?id=215375 According to rpm -q --changelog kernel-default-5.14.21-150400.24.38.1.x86_64 it seems as if that particular commit is not part of the RPM. But it looks like some other commit was added/backported to 5.14.21-150400.24.38.1 that accidentally disables 1.0 and/or NTLM? While I'm all in favor of removing cryptographically weak protocols it shouldn't be done w/o some sort of announcement/warning because I'm guessing that there are quite a few devices which only offer services via 1.0 and/or NTLM. Regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024
Am 03.01.23 um 20:55 schrieb Till Dörges:
On 02.01.23 16:41, Till Dörges wrote:
On 02.01.23 05:43, Felix Miata wrote:
5.14.21-150400.24.38-default boots, but I can't use it, because OS/2 connectivity is a must. 5.14.21-150400.24.33-default solves the problem, keeps OS/2 connected. [...] mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
I also observe a regression with openSUSE Leap 15.4 (x86-64) for SMB mounts between these two kernels:
ok kernel-default-5.14.21-150400.24.33.2.x86_64 FAIL kernel-default-5.14.21-150400.24.38.1.x86_64
Failing SMB shares are configured with CIFS version 1.0. (I know, you're not supposed to use 1.0, but I'm not calling the shots on that one.)
Error reported by mount is different, though:
- Exit code 32 - Return code 20 (not a directory)
The share in question is configured with CIFS version 1.0 and security mode NTLM.
I haven't found a bugzilla entry on b.o.o.
Upstream apparently has gotten rid of NTLM already:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i...
Also this upstream bug seems to be related:
https://bugzilla.kernel.org/show_bug.cgi?id=215375
According to
rpm -q --changelog kernel-default-5.14.21-150400.24.38.1.x86_64
it seems as if that particular commit is not part of the RPM.
But it looks like some other commit was added/backported to 5.14.21-150400.24.38.1 that accidentally disables 1.0 and/or NTLM?
While I'm all in favor of removing cryptographically weak protocols it shouldn't be done w/o some sort of announcement/warning because I'm guessing that there are quite a few devices which only offer services via 1.0 and/or NTLM.
Regards -- Till
i am not sure if it will help you: i have to connect to a windows 98 (more or less embedded system) on a mechanical machine. with tumbleweed 20230102 kernel 6.1.1-1-default and with the samba stuff from: /repositories/home%3A/laxity/openSUSE_Tumbleweed/x86_64 i am able to mount to it (without a password, with password not possible) and the windows machine is able to mount to my samba folder on my linux machine. i have no idea what i will do if this stopps. i am 52 years old, i like to use this machine about 13 years more, its from Italy and the people who have assembled and programmed and designed this machine where about 15-20 years in advanced of a German or other countries mechanical machine design. so for me this machine is not more than 7 years old. i am on opensuselinux because here i was always able to find a solution to connect and have a system that do what i tell him. but in the last 2 years i feel linux will loose this. :-((( simoN -- www.becherer.de ----------------------------------------------- - Das ist die vorlaeufig endgueltige Version! - Herbert C. Maier Dipl.-Ing. (FH) -----------------------------------------------
On 2023-01-03 22:02, Simon Becherer wrote:
Am 03.01.23 um 20:55 schrieb Till Dörges:
On 02.01.23 16:41, Till Dörges wrote:
On 02.01.23 05:43, Felix Miata wrote:
...
i am not sure if it will help you:
i have to connect to a windows 98 (more or less embedded system) on a mechanical machine. with tumbleweed 20230102 kernel 6.1.1-1-default and with the samba stuff from: /repositories/home%3A/laxity/openSUSE_Tumbleweed/x86_64 i am able to mount to it (without a password, with password not possible) and the windows machine is able to mount to my samba folder on my linux machine.
i have no idea what i will do if this stopps. i am 52 years old, i like to use this machine about 13 years more, its from Italy and the people who have assembled and programmed and designed this machine where about 15-20 years in advanced of a German or other countries mechanical machine design. so for me this machine is not more than 7 years old.
i am on opensuselinux because here i was always able to find a solution to connect and have a system that do what i tell him. but in the last 2 years i feel linux will loose this. :-(((
Well, you probably need to connect to that machine with an old Linux machine, in an isolated network. You might put an intermediate old linux machine in the middle, bridging between the old and the new samba. Serving the same directory with two samba versions to two different networks. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am 03.01.23 um 20:55 schrieb Till Dörges:
On 02.01.23 16:41, Till Dörges wrote:
On 02.01.23 05:43, Felix Miata wrote:
5.14.21-150400.24.38-default boots, but I can't use it, because OS/2 connectivity is a must. 5.14.21-150400.24.33-default solves the problem, keeps OS/2 connected. [...] mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
I also observe a regression with openSUSE Leap 15.4 (x86-64) for SMB mounts between these two kernels:
ok kernel-default-5.14.21-150400.24.33.2.x86_64 FAIL kernel-default-5.14.21-150400.24.38.1.x86_64
Failing SMB shares are configured with CIFS version 1.0. (I know, you're not supposed to use 1.0, but I'm not calling the shots on that one.)
Error reported by mount is different, though:
- Exit code 32 - Return code 20 (not a directory)
The share in question is configured with CIFS version 1.0 and security mode NTLM.
I haven't found a bugzilla entry on b.o.o.
I guess this is probably https://bugzilla.opensuse.org/show_bug.cgi?id=1206935 reported on Friday. Happens for me too, smb connection to a Win2000 VM, 5.14.21-150400.24.38-default is broken, 5.14.21-150400.24.33-default works.
Upstream apparently has gotten rid of NTLM already:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i...
Also this upstream bug seems to be related:
https://bugzilla.kernel.org/show_bug.cgi?id=215375
According to
rpm -q --changelog kernel-default-5.14.21-150400.24.38.1.x86_64
it seems as if that particular commit is not part of the RPM.
But it looks like some other commit was added/backported to 5.14.21-150400.24.38.1 that accidentally disables 1.0 and/or NTLM?
While I'm all in favor of removing cryptographically weak protocols it shouldn't be done w/o some sort of announcement/warning because I'm guessing that there are quite a few devices which only offer services via 1.0 and/or NTLM.
Regards -- Till
participants (5)
-
Carlos E. R. -
Felix Miata -
Manfred Schwarb -
Simon Becherer -
Till Dörges