netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 213827] New: Stall In TCP/IP
Date: Thu, 22 Jul 2021 15:16:06 -0700	[thread overview]
Message-ID: <20210722151606.4dd189da@hermes.local> (raw)



Begin forwarded message:

Date: Thu, 22 Jul 2021 22:03:50 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 213827] New: Stall In TCP/IP


https://bugzilla.kernel.org/show_bug.cgi?id=213827

            Bug ID: 213827
           Summary: Stall In TCP/IP
           Product: Networking
           Version: 2.5
    Kernel Version: Observed 5.9.2. Confirmed on 5.12 and 5.13
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: martenst@crankuptheamps.com
        Regression: No

Created attachment 298007
  --> https://bugzilla.kernel.org/attachment.cgi?id=298007&action=edit  
A basic repro of the observed issue.

We see an unexpected pause of 3-60 seconds where the test no longer receives
data, recv() is blocking, netstat shows data is sitting in the 7777 server's
send queue and 0 bytes are in the test's receive queue.

Setting net.core.rmem_max seems to be a key factor. For our testing we used
net.core.rmem_max=16777216

See attached README and repro.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-07-22 22:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210722151606.4dd189da@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).