cinap_lenrek 8152e9d075 devip: tcp: Don't respond to FIN-less ACKs during TIME-WAIT (thanks Barret Rhoden) ... Under the normal close sequence, when we receive a FIN|ACK, we enter TIME-WAIT and respond to that LAST-ACK with an ACK. Our TCP stack would send an ACK in response to *any* ACK, which included FIN|ACK but also included regular ACKs. (Or PSH|ACKs, which is what we were actually getting/sending). That was more ACKs than is necessary and results in an endless ACK storm if we were under the simultaneous close sequence. In that scenario, both sides of a connection are in TIME-WAIT. Both sides receive FIN|ACK, and both respond with an ACK. Then both sides receive *those* ACKs, and respond again. This continues until the TIME-WAIT wait period elapses and each side's TCP timers (in the Plan 9 / Akaros case) shut down. The fix for this is to only respond to a FIN|ACK when we are in TIME-WAIT.		2019-01-27 22:12:50 +01:00
..
doc	/sys/doc: fix mkfile to and remove files that now can be regenerated	2017-05-09 16:23:48 +02:00
games/lib	fortunes: [9fans] ..... UNSUBSCRIBE_HELP NEEDED	2018-12-11 12:57:36 -05:00
include	dtracy: get rid of DTName struct, support more than three parts in a probe name, wildcard matching	2018-12-13 10:42:49 +00:00
lib	troff: fix -ms mug (thanks aksr)	2019-01-23 21:28:22 +01:00
man	dhcpd(8), ndb(6): group related ndb attributes together	2019-01-24 20:30:14 +01:00
src	devip: tcp: Don't respond to FIN-less ACKs during TIME-WAIT (thanks Barret Rhoden)	2019-01-27 22:12:50 +01:00