cifs: Silently ignore unknown oplock break handle
authorVincent Whitchurch <vincent.whitchurch@axis.com>
Fri, 19 Mar 2021 13:57:11 +0000 (14:57 +0100)
committerSteve French <stfrench@microsoft.com>
Fri, 26 Mar 2021 23:05:26 +0000 (18:05 -0500)
commit219481a8f90ec3a5eed9638fb35609e4b1aeece7
tree1438bef3fa4e1081fb5223570265348a04202665
parentcee8f4f6fcabfdf229542926128e9874d19016d5
cifs: Silently ignore unknown oplock break handle

Make SMB2 not print out an error when an oplock break is received for an
unknown handle, similar to SMB1.  The debug message which is printed for
these unknown handles may also be misleading, so fix that too.

The SMB2 lease break path is not affected by this patch.

Without this, a program which writes to a file from one thread, and
opens, reads, and writes the same file from another thread triggers the
below errors several times a minute when run against a Samba server
configured with "smb2 leases = no".

 CIFS: VFS: \\192.168.0.1 No task to wake, unknown frame received! NumMids 2
 00000000424d53fe 00000040 00000000 00000012  .SMB@...........
 0000001000000001 00000000 ffffffff ffffffff  ................
 0000002000000000 00000000 00000000 00000000  ................
 0000003000000000 00000000 00000000 00000000  ................

Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
Reviewed-by: Tom Talpey <tom@talpey.com>
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
Signed-off-by: Steve French <stfrench@microsoft.com>
fs/cifs/smb2misc.c