Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 15136] New: Access to cifs gets stuck for a while (>20s) after disconnecting from network
Date: Thu, 04 Aug 2022 03:01:40 +0000	[thread overview]
Message-ID: <bug-15136-10630@https.bugzilla.samba.org/> (raw)

https://bugzilla.samba.org/show_bug.cgi?id=15136

            Bug ID: 15136
           Summary: Access to cifs gets stuck for a while (>20s) after
                    disconnecting from network
           Product: CifsVFS
           Version: 4.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: kernel fs
          Assignee: sfrench@samba.org
          Reporter: wangrong@uniontech.com
        QA Contact: cifs-qa@samba.org
  Target Milestone: ---

Created attachment 17460
  --> https://bugzilla.samba.org/attachment.cgi?id=17460&action=edit
patch for code update

After the network is interrupted, a new SMB request will wait for a
fixed 10 seconds for network reconnection before sending, and return an
error if it times out.

Because 10 seconds is too long and there are operation retries, system
calls (such as stat) take a long time (greater than 20 seconds), which
makes application respond slowly.

Here, the duration of waiting for network reconnection is exposed to
the user space through the mount option, which is convenient for users
and applications to set according to the actual situation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

             reply	other threads:[~2022-08-04  3:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  3:01 samba-bugs [this message]
2022-08-04 14:05 ` [Bug 15136] Access to cifs gets stuck for a while (>20s) after disconnecting from network samba-bugs
2022-08-05  3:14 ` samba-bugs

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=bug-15136-10630@https.bugzilla.samba.org/ \
    --to=samba-bugs@samba.org \
    --cc=cifs-qa@samba.org \
    /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