netdev - [TCP_CA_CWR] Causes for entering TCP_CA_CWR state with 0 retransmissions

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

Message-ID: <46bf9ede0907141138q3b665aefv46a18591c3cfc2ce@mail.gmail.com>
Date:	Tue, 14 Jul 2009 14:38:07 -0400
From:	Yinglin Sun <yinglin.s@...il.com>
To:	netdev@...r.kernel.org
Subject: [TCP_CA_CWR] Causes for entering TCP_CA_CWR state with 0 
	retransmissions

Hi,

I have a question about tcp_ca_state "TCP_CA_CWR".  Under what
circumstances does it enter this state?
I'm doing some experiments and have trace from tcp_info. From tcp_info
trace, I found that many places show ca_state is 2 (TCP_CA_CWR). Under
this state, the congestion window size decreases but the total number
of retransmissions is still 0.

I got some explanation from a very old message posted in 2003:
TCP_CA_CWR: The congestion window should be reduced due to some
congestion notification event, which can be ECN, ICMP source quench,
or local device congestion. Both sender and receiver don't have ECN
enabled, so ECN is not the case. ICMP source quench is so out-of-date
with RFC 1812 saying the routers should not issue these packets. So it
might be caused by local congestion. But this post is too old, almost
done 6 years ago. So I want to check if there are other possible
causes in today's kernel leading to TCP_CA_CWR with 0 retransmissions?

I need to find the exact cause for this phenomena, local congestion,
or other possible causes. Any hint will be very helpful for me.

Thanks a lot!

Yinglin
--
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