diff options
| author | Steve French <stfrench@microsoft.com> | 2024-07-23 00:44:48 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-08-03 08:54:16 +0200 |
| commit | f2d6c5b8ef1169e9d012d34069e5c4e9cf9e7849 (patch) | |
| tree | 4922902e598541b0393dbbff2cd799150faab59d /security/keys | |
| parent | 31553d20b4220f9fca479a6965db57d09b1ab039 (diff) | |
| download | linux-f2d6c5b8ef1169e9d012d34069e5c4e9cf9e7849.tar.gz linux-f2d6c5b8ef1169e9d012d34069e5c4e9cf9e7849.tar.bz2 linux-f2d6c5b8ef1169e9d012d34069e5c4e9cf9e7849.zip | |
cifs: mount with "unix" mount option for SMB1 incorrectly handled
commit 0e314e452687ce0ec5874e42cdb993a34325d3d2 upstream.
Although by default we negotiate CIFS Unix Extensions for SMB1 mounts to
Samba (and they work if the user does not specify "unix" or "posix" or
"linux" on mount), and we do properly handle when a user turns them off
with "nounix" mount parm. But with the changes to the mount API we
broke cases where the user explicitly specifies the "unix" option (or
equivalently "linux" or "posix") on mount with vers=1.0 to Samba or other
servers which support the CIFS Unix Extensions.
"mount error(95): Operation not supported"
and logged:
"CIFS: VFS: Check vers= mount option. SMB3.11 disabled but required for POSIX extensions"
even though CIFS Unix Extensions are supported for vers=1.0 This patch fixes
the case where the user specifies both "unix" (or equivalently "posix" or
"linux") and "vers=1.0" on mount to a server which supports the
CIFS Unix Extensions.
Cc: stable@vger.kernel.org
Reviewed-by: David Howells <dhowell@redhat.com>
Reviewed-by: Paulo Alcantara (Red Hat) <pc@manguebit.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security/keys')
0 files changed, 0 insertions, 0 deletions