[Bug 265588] [TCP] - tcp send a retransmission identical sequence number packet with different payload

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588

Hans Petter Selasky <hselasky@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hselasky@FreeBSD.org

--- Comment #12 from Hans Petter Selasky <hselasky@FreeBSD.org> ---
Are you using the latest Linux kernel? I noticed something strange when copying
files to a Linux box using scp recently (I'm using 14-main GENERIC-NODEBUG) and
the problems recently disappeared. Did you check the Linux tcp commits
recently?

For example this one:

commit 686dc2db2a0fdc1d34b424ec2c0a735becd8d62b
Author: Neal Cardwell <ncardwell@google.com>
Date:   Sat Sep 3 08:10:23 2022 -0400

    tcp: fix early ETIMEDOUT after spurious non-SACK RTO

    Fix a bug reported and analyzed by Nagaraj Arankal, where the handling
    of a spurious non-SACK RTO could cause a connection to fail to clear
    retrans_stamp, causing a later RTO to very prematurely time out the
    connection with ETIMEDOUT.

    Here is the buggy scenario, expanding upon Nagaraj Arankal's excellent
    report:

https://github.com/LineageOS/android_kernel_xiaomi_onclite/commit/be8176c25c32607cf357317880038a1e4a935bd7

--HPS

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