Files
android_kernel_xiaomi_sm8450/net/ipv4
Ilpo Järvinen e1cd8f78f8 [TCP] FRTO: Clear frto_highmark only after process_frto that uses it
I broke this in commit 3de96471bd:

	[TCP]: Wrap-safed reordering detection FRTO check

tcp_process_frto should always see a valid frto_highmark. An invalid
frto_highmark (zero) is very likely what ultimately caused a seqno
compare in tcp_frto_enter_loss to do the wrong leading to the LOST-bit
leak.

Having LOST-bits integry ensured like done after commit
23aeeec365:

	[TCP] FRTO: Plug potential LOST-bit leak

won't hurt. It may still be useful in some other, possibly legimate,
scenario.

Reported by Chazarain Guillaume <guichaz@yahoo.fr>.

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-14 15:55:09 -08:00
..
2007-11-12 21:25:24 -08:00
2007-11-02 08:47:06 +01:00
2007-10-19 11:53:41 -07:00
2007-10-26 04:06:08 -07:00
2007-10-14 12:41:52 -07:00
2007-10-15 12:26:35 -07:00
2007-10-15 12:26:35 -07:00
2007-10-20 01:34:40 +02:00
2007-04-25 22:28:20 -07:00
2007-10-10 16:48:31 -07:00