linux-kernel - Regression -- linux 5.5.3: can no longer mount with unix extentions using cifs 2.1 (Win10-only client additions)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 22 Feb 2020 17:52:42 -0800
From:   L Walsh <cifs@...nx.org>
To:     linux-cifs <linux-cifs@...r.kernel.org>,
        Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Regression -- linux 5.5.3: can no longer mount with unix extentions
 using cifs 2.1 (Win10-only client additions)

hard links and serverino numbers, among other things used to work when
mounting a win7 client using a linux cifs client

I tried this today, and am getting:

[701913.978407] CIFS VFS: Autodisabling the use of server inode numbers 
on \\Athenae\C.
[701913.986151] CIFS VFS: The server doesn't seem to support them 
properly or the files might be on different servers (DFS).
[701913.997116] CIFS VFS: Hardlinks will not be recognized on this 
mount. Consider mounting with the "noserverino" option to silence this 
message.
[703793.287615] CIFS VFS: Server does not support mounting with posix 
SMB3.11 extensions.
[703793.295810] CIFS VFS: cifs_mount failed w/return code = -95

The win7 workstation in question is running 1 hard disk, no DFS.

Unix extensions worked long before SMB3.x.  It seems there is ongoing work
to disable SMB2.1 support and replace it with only latest SMB from MS
compatible with Win10. 

If MS wants to backport SMB3.x to Win7, that would be fine, but I
doubt that is going to happen.  NTL, if they keep breaking 2.1 compatibility
that would be one option.