From: Pavel Shilovsky <piastryyy@gmail.com>
To: Moritz M <mailinglist@moritzmueller.ee>
Cc: linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: Possible timeout problem when opening a file twice on a SMB mount
Date: Thu, 31 Oct 2019 14:01:24 -0700 [thread overview]
Message-ID: <CAKywueTqA+=8Hv9F=BGbUGnv9HjURxY6kKzrMvE2LG-Dq+9t_A@mail.gmail.com> (raw)
In-Reply-To: <6a49aa3e2cf17975efc5259f94c01ce7@moritzmueller.ee>
чт, 31 окт. 2019 г. в 02:20, Moritz M <mailinglist@moritzmueller.ee>:
>
> Hi Pavel,
>
> Am 2019-10-30 22:51, schrieb Pavel Shilovsky:
> > I think there is a difference in your setup between v5.2.21 and v5.3.7
> > kernels. I found the issue in oplock break processing that can happen
> > if you have several shares from the same server mounted on the client.
>
> I think you are right. Usually I mount multiple shares from one server.
> It could had happened that I tested it with just one share mounted when
> using the
> v5.2 Kernel.
>
>
> > Could you test the patch to see if it works for your environment?
>
> I did and it worked ;)
>
> Thanks.
Thanks for verifying the fix! I will post the patch to the list soon.
--
Best regards,
Pavel Shilovsky
next prev parent reply other threads:[~2019-10-31 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 10:57 Possible timeout problem when opening a file twice on a SMB mount Moritz M
2019-09-20 23:26 ` Pavel Shilovsky
2019-09-23 14:04 ` Moritz M
2019-09-24 18:11 ` ronnie sahlberg
2019-09-24 19:05 ` Pavel Shilovsky
2019-09-24 21:06 ` Pavel Shilovsky
2019-09-25 19:23 ` Moritz M
2019-09-25 20:54 ` Pavel Shilovsky
2019-09-26 10:53 ` Moritz M
2019-09-26 18:58 ` Pavel Shilovsky
2019-10-30 13:26 ` Moritz M
2019-10-30 21:51 ` Pavel Shilovsky
2019-10-31 9:20 ` Moritz M
2019-10-31 21:01 ` Pavel Shilovsky [this message]
2019-09-24 19:33 ` Moritz M
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='CAKywueTqA+=8Hv9F=BGbUGnv9HjURxY6kKzrMvE2LG-Dq+9t_A@mail.gmail.com' \
--to=piastryyy@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=mailinglist@moritzmueller.ee \
/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;
as well as URLs for NNTP newsgroup(s).