cifs: version operations for smb20 unneeded when legacy support disabled
authorSteve French <stfrench@microsoft.com>
Thu, 2 Jun 2022 03:08:46 +0000 (22:08 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 14 Jun 2022 16:36:24 +0000 (18:36 +0200)
commitdc105d20122d20784d145216d0ed89929d5ceb0d
treeb49538e8e5bcbd2819ad919c433ed44afb641183
parent12eb4e7db22a5a3fc99a122b4b3a9f1b9723d7aa
cifs: version operations for smb20 unneeded when legacy support disabled

[ Upstream commit 7ef93ffccd55fb0ba000ed16ef6a81cd7dee07b5 ]

We should not be including unused smb20 specific code when legacy
support is disabled (CONFIG_CIFS_ALLOW_INSECURE_LEGACY turned
off).  For example smb2_operations and smb2_values aren't used
in that case.  Over time we can move more and more SMB1/CIFS and SMB2.0
code into the insecure legacy ifdefs

Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/cifs/cifsglob.h
fs/cifs/smb2ops.c