From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 218937] New: TCP connection frozen on sender and receiver. No retries beyond 1.
Date: Wed, 5 Jun 2024 09:06:35 -0700 [thread overview]
Message-ID: <20240605090635.30c22c8b@hermes.local> (raw)
Begin forwarded message:
Date: Wed, 05 Jun 2024 06:26:40 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 218937] New: TCP connection frozen on sender and receiver. No retries beyond 1.
https://bugzilla.kernel.org/show_bug.cgi?id=218937
Bug ID: 218937
Summary: TCP connection frozen on sender and receiver. No
retries beyond 1.
Product: Networking
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: stephen@networkplumber.org
Reporter: joysonanuit@gmail.com
Regression: No
Created attachment 306413
--> https://bugzilla.kernel.org/attachment.cgi?id=306413&action=edit
sender pcap screenshot
Hi,
i am facing an issue in TCP. At a random point in packet transfer, sender
stops retrying and receiver stops acking. our previous kernel was 2.6 and
current kernel is 5.4. the sequence of events are as below.
sender:
sends few packets of data.
misses a few ACKs.
retries again.
does not get an ack.
stops
receiver:
receives the packets.
sends ack to only few packets.
does not retry ack for the remaining packets.
for this FIN, the sender sends RST.
there is a timeout at receiver end which forces the socket to be closed.
this erroneous socket reaches the end of timeout and sends a FIN with ACK of
all the data that it has received(including the ones that it did not ack and
the sender was waiting for)
--
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:[~2024-06-05 16:06 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=20240605090635.30c22c8b@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