From: Paulo Alcantara <pc@cjr.nz>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>,
Steve French <sfrench@samba.org>
Cc: kernel@axis.com, tom@talpey.com,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] cifs: Silently ignore unknown oplock break handle
Date: Thu, 25 Mar 2021 12:32:55 -0300 [thread overview]
Message-ID: <871rc3fdug.fsf@cjr.nz> (raw)
In-Reply-To: <20210319135711.11802-1-vincent.whitchurch@axis.com>
Vincent Whitchurch <vincent.whitchurch@axis.com> writes:
> 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
> 00000000: 424d53fe 00000040 00000000 00000012 .SMB@...........
> 00000010: 00000001 00000000 ffffffff ffffffff ................
> 00000020: 00000000 00000000 00000000 00000000 ................
> 00000030: 00000000 00000000 00000000 00000000 ................
>
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
>
> Notes:
> v3:
> - Change debug print to Tom Talpey's suggestion
>
> v2:
> - Drop change to lease break
> - Rewrite commit message
>
> fs/cifs/smb2misc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
prev parent reply other threads:[~2021-03-25 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 13:57 [PATCH v3] cifs: Silently ignore unknown oplock break handle Vincent Whitchurch
2021-03-19 14:03 ` Tom Talpey
2021-03-25 15:21 ` Steve French
2021-03-25 15:32 ` Paulo Alcantara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rc3fdug.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=kernel@axis.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=tom@talpey.com \
--cc=vincent.whitchurch@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox