Here is updated patch which following Pavel's suggestion simply removes the sometimes confusing warning rather than make a more complex change which checks for whether the packet was decrypted earlier or not On Tue, Nov 5, 2019 at 4:47 PM Steve French wrote: > > 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 ..." > > -- > Thanks, > > Steve -- Thanks, Steve