diff options
| author | Steve French | 2023-08-24 23:29:18 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman | 2023-09-19 12:27:56 +0200 |
| commit | 0f7339056893f270e391c23d2438871a79deec86 (patch) | |
| tree | aac63c14e00eda93ec52d201cb34c922e1f3fa17 /drivers/nvme | |
| parent | 22ec50d7b524183513721fdf05a5c20fa6656639 (diff) | |
send channel sequence number in SMB3 requests after reconnects
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>
Diffstat (limited to 'drivers/nvme')
0 files changed, 0 insertions, 0 deletions