kernel/git/stable/linux.git/fs/smb/common, branch linux-6.5.yLinux kernel stable treehttps://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=linux-6.5.y2023-09-19T10:30:11+00:00send channel sequence number in SMB3 requests after reconnects2023-09-19T10:30:11+00:00Steve Frenchstfrench@microsoft.com2023-08-25T04:29:18+00:00urn:sha1:cbf06d3e0271f3b9c7590d865acb576ce9911291
commit 09ee7a3bf866c0fa5ee1914d2c65958559eb5b4c upstream.
The ChannelSequence field in the SMB3 header is supposed to be
increased after reconnect to allow the server to distinguish
requests from before and after the reconnect. We had always
been setting it to zero. There are cases where incrementing
ChannelSequence on requests after network reconnects can reduce
the chance of data corruptions.
See MS-SMB2 3.2.4.1 and 3.2.7.1
Signed-off-by: Steve French <stfrench@microsoft.com>
Cc: stable@vger.kernel.org # 5.16+
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
smb: move client and server files to common directory fs/smb2023-05-24T21:29:21+00:00Steve Frenchstfrench@microsoft.com2023-05-22T01:46:30+00:00urn:sha1:38c8a9a52082579090e34c033d439ed2cd1a462d
Move CIFS/SMB3 related client and server files (cifs.ko and ksmbd.ko
and helper modules) to new fs/smb subdirectory:
fs/cifs --> fs/smb/client
fs/ksmbd --> fs/smb/server
fs/smbfs_common --> fs/smb/common
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Signed-off-by: Steve French <stfrench@microsoft.com>