netdev - Re: [PATCH net-next] tcp: reset timer after any SYNACK retransmit

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 29 Apr 2013 15:13:34 -0700
From:	Yuchung Cheng <ycheng@...gle.com>
To:	David Miller <davem@...emloft.net>
Cc:	Neal Cardwell <ncardwell@...gle.com>,
	Eric Dumazet <edumazet@...gle.com>,
	Hagen Paul Pfeifer <hagen@...u.net>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] tcp: reset timer after any SYNACK retransmit

On Mon, Apr 29, 2013 at 12:17 PM, David Miller <davem@...emloft.net> wrote:
> From: Yuchung Cheng <ycheng@...gle.com>
> Date: Mon, 29 Apr 2013 11:44:51 -0700
>
>> Linux immediately returns SYNACK on (spurious) SYN retransmits, but
>> keeps the SYNACK timer running independently. Thus the timer may
>> fire right after the SYNACK retransmit and causes a SYN-SYNACK
>> cross-fire burst.
>>
>> Adopt the fast retransmit/recovery idea in established state by
>> re-arming the SYNACK timer after the fast (SYNACK) retransmit. The
>> timer may fire late up to 500ms due to the current SYNACK timer wheel,
>> but it's OK to be conservative when network is congested. Eric's new
>> listener design should address this issue.
>>
>> Signed-off-by: Yuchung Cheng <ycheng@...gle.com>
>
> Applied.
>
> Maybe -stable material?
Should be fine for -stable too. Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html