From: Eric Dumazet Date: Mon, 1 Oct 2007 20:58:36 +0000 (-0700) Subject: [TCP]: secure_tcp_sequence_number() should not use a too fast clock X-Git-Tag: v2.6.23~42^2~1 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9b42c336d06411e6463949d2dac63949f66ff70b;p=pandora-kernel.git [TCP]: secure_tcp_sequence_number() should not use a too fast clock TCP V4 sequence numbers are 32bits, and RFC 793 assumed a 250 KHz clock. In order to follow network speed increase, we can use a faster clock, but we should limit this clock so that the delay between two rollovers is greater than MSL (TCP Maximum Segment Lifetime : 2 minutes) Choosing a 64 nsec clock should be OK, since the rollovers occur every 274 seconds. Problem spotted by Denys Fedoryshchenko [ This bug was introduced by f85958151900f9d30fa5ff941b0ce71eaa45a7de ] Signed-off-by: Eric Dumazet Signed-off-by: David S. Miller --- Reading git-diff-tree failed