| 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
| ||
|
Date: Thu, 08 Jan 2015 10:52:58 -0800 From: Rick Jones <rick.jones2@...com> To: Eric Dumazet <eric.dumazet@...il.com>, Erik Grinaker <erik@...gler.no> CC: Yuchung Cheng <ycheng@...gle.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, netdev <netdev@...r.kernel.org> Subject: Re: TCP connection issues against Amazon S3 > Strange thing is that sender does not misbehave at the beginning when > receiver window is still small. Only after a while. Just guessing, but when the receiver window is small, the sender cannot get a large quantity of data out there at once, so any string of lost packets will tend to be smaller. If the sender is relying on the RTO to trigger the retransmits, and is not resetting his RTO until the clean ACK of a segment sent after snd_nxt when the loss is detected, the smaller loss strings will not get to the rather large RTO values seen in the trace before curl gives-up. It may be that the sender is indeed misbehaving at the beginning, just that it isn't noticeable? Different but perhaps related observation/question - without timestamps (which we don't have in this case), isn't there a certain ambiguity about arriving out-of-order segments? One doesn't really know if they are out-of-order because the network is re-ordering, or because they are retransmissions of segments we've not yet seen at the receiver. rick -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists