netdev - Fw: [Bug 218937] New: TCP connection frozen on sender and receiver. No retries beyond 1.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Wed, 5 Jun 2024 09:06:35 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Fw: [Bug 218937] New: TCP connection frozen on sender and receiver.
 No retries beyond 1.

Begin forwarded message:

Date: Wed, 05 Jun 2024 06:26:40 +0000
From: bugzilla-daemon@...nel.org
To: stephen@...workplumber.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@...workplumber.org
          Reporter: joysonanuit@...il.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.