smb3: remove confusing dmesg when mounting with encryption ("seal")
authorSteve French <stfrench@microsoft.com>
Fri, 8 Nov 2019 07:01:35 +0000 (01:01 -0600)
committerSteve French <stfrench@microsoft.com>
Mon, 25 Nov 2019 07:14:53 +0000 (01:14 -0600)
commit037d050724ed30a5ef02e6e886884a48e7654e47
tree434f8a2856b36cb1f3e07741a81991992a8f588d
parent72e73c78c446e3c009a29b017c7fa3d79463e2aa
smb3: remove confusing dmesg when mounting with encryption ("seal")

The smb2/smb3 message checking code was logging to dmesg when mounting
with encryption ("seal") for compounded SMB3 requests.  When encrypted
the whole frame (including potentially multiple compounds) is read
so the length field is longer than in the case of non-encrypted
case (where length field will match the the calculated length for
the particular SMB3 request in the compound being validated).

Avoids the warning on mount (with "seal"):

   "srv rsp padded more than expected. Length 384 not ..."

Signed-off-by: Steve French <stfrench@microsoft.com>
fs/cifs/smb2misc.c