]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
Fix SMB311 posix special file creation to servers which do not advertise reparse...
authorSteve French <stfrench@microsoft.com>
Tue, 15 Jul 2025 03:16:19 +0000 (22:16 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 24 Jul 2025 06:58:26 +0000 (08:58 +0200)
commit2f3d117ee1eca107e84911b1b6b8651e64283f2c
tree01afd0328c8c0ce1e59900482e21e508c79ad195
parent5dfbdc99416521b57d01bc40feffc4b43701282a
Fix SMB311 posix special file creation to servers which do not advertise reparse support

commit 8767cb3fbd514c4cf85b4f516ca30388e846f540 upstream.

Some servers (including Samba), support the SMB3.1.1 POSIX Extensions (which use reparse
points for handling special files) but do not properly advertise file system attribute
FILE_SUPPORTS_REPARSE_POINTS.  Although we don't check for this attribute flag when
querying special file information, we do check it when creating special files which
causes them to fail unnecessarily.   If we have negotiated SMB3.1.1 POSIX Extensions
with the server we can expect the server to support creating special files via
reparse points, and even if the server fails the operation due to really forbidding
creating special files, then it should be no problem and is more likely to return a
more accurate rc in any case (e.g. EACCES instead of EOPNOTSUPP).

Allow creating special files as long as the server supports either reparse points
or the SMB3.1.1 POSIX Extensions (note that if the "sfu" mount option is specified
it uses a different way of storing special files that does not rely on reparse points).

Cc: <stable@vger.kernel.org>
Fixes: 6c06be908ca19 ("cifs: Check if server supports reparse points before using them")
Acked-by: Ralph Boehme <slow@samba.org>
Acked-by: Paulo Alcantara (Red Hat) <pc@manguebit.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/smb/client/smb2inode.c
fs/smb/client/smb2ops.c