Kernel 6.6.1 breaks cifs?

English Applications
1

Hi,

Tumbleweed, up-to-date.

I’m using smb4k to mount remote cifs-shares via vpn.

Doesn’t work with kernel 6.6.1, works with kernel 6.5.9

It seems there is an issue with cifs and kernel 6.6, see here:

While my error message in dmesg is different –

CIFS: Attempting to mount //sbsABCD/XYZ
[ 4722.266410] CIFS: VFS: cifs_mount failed w/return code = -4

–

BUT if there really were an issue, there would be many reports. Maybe kernel
6.6.1 is too new?

Back on 6.5.9 for the time being.

2

Sometimes, a cifs_mount code -4 in the log file is followed by a detail line (as error 4 is a general error). Please show more of the dmseg output.

Also, Is this share DFS related?

3

I’ve never heard of DFS and after a quick look into it, I don’t think so, because it all worked for years, still works with the older kernel and all shares reside on the same physical server.

kernel 6.5.9, mounting the shares, dmesg:

[ 2474.704244] Key type dns_resolver registered
[ 2474.813664] Key type cifs.spnego registered
[ 2474.813682] Key type cifs.idmap registered
[ 2474.814304] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[ 2474.814307] CIFS: Attempting to mount //sbs1234/ShareA
[ 2475.721425] CIFS: Attempting to mount //sbs1234/ShareB
[ 2476.467871] CIFS: Attempting to mount //sbs1234/ShareC
[ 2477.185436] CIFS: Attempting to mount //dsrvABCD/ShareD

kernel 6.6.1, mounting not possible, dmesg:

[   69.457034] Key type dns_resolver registered
[   69.577215] Key type cifs.spnego registered
[   69.577232] Key type cifs.idmap registered
[   69.577843] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[   69.577846] CIFS: Attempting to mount //sbs1234/ShareA
[   69.587109] CIFS: VFS: cifs_mount failed w/return code = -4
[   69.671802] CIFS: Attempting to mount //sbs1234/ShareB
[   69.680376] CIFS: VFS: cifs_mount failed w/return code = -4
[   69.706663] CIFS: Attempting to mount //sbs1234/ShareC
[   69.713894] CIFS: VFS: cifs_mount failed w/return code = -4
[   69.799015] CIFS: Attempting to mount //dsrvABCD/ShareD
[   69.806418] CIFS: VFS: cifs_mount failed w/return code = -4

smb4k itself reports:

mount error(4): Interrupted system call
4

Doesn‘t the output tell you that you are using an unsecure SMB1 and if you want to use it any langer what to do?

I would try that first…

5

No, the output says in both cases no dialect specified and if SMB1 needed, specify vers=1.0 on mount. Besides this, I even tried SMB1, without success.

6

Bugreport:

https://bugzilla.opensuse.org/show_bug.cgi?id=1217310

7

I’m in my office now and mounting the server shares works with kernel 6.6.1, so the culprit is the tunnel. But still out of ideas. The VPN used to work for years and still works under the old kernel. Has something else changed with the new kernel?