diff options
| author |   Roberto Bergantinos Corpas <rbergant@redhat.com> | 2019-10-14 10:59:23 +0200 |
|---|---|---|
| committer |   Steve French <stfrench@microsoft.com> | 2019-10-20 19:19:49 -0500 |
| commit | 03d9a9fe3f3aec508e485dd3dcfa1e99933b4bdb (patch) | |
| tree | 73bb8587830b41af04ab1e8d3824133cd003ee47 /fs/cifs/connect.c | |
| parent | cifs: clarify comment about timestamp granularity for old servers (diff) | |
| download | linux-dev-03d9a9fe3f3aec508e485dd3dcfa1e99933b4bdb.tar.xz linux-dev-03d9a9fe3f3aec508e485dd3dcfa1e99933b4bdb.zip | |
CIFS: avoid using MID 0xFFFF
According to MS-CIFS specification MID 0xFFFF should not be used by the
CIFS client, but we actually do. Besides, this has proven to cause races
leading to oops between SendReceive2/cifs_demultiplex_thread. On SMB1,
MID is a 2 byte value easy to reach in CurrentMid which may conflict with
an oplock break notification request coming from server
Signed-off-by: Roberto Bergantinos Corpas <rbergant@redhat.com>
Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
Reviewed-by: Aurelien Aptel <aaptel@suse.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
CC: Stable <stable@vger.kernel.org>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions