Eric Dumazet 9b42c336d0 [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 <dada1@cosmosbay.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-10-01 21:01:24 -07:00
..
2007-07-31 15:39:44 -07:00
2007-08-22 19:52:44 -07:00
2007-07-16 09:05:46 -07:00
2007-05-08 11:15:09 -07:00
2007-05-08 11:15:13 -07:00
2007-05-21 09:18:19 -07:00
2007-07-17 10:23:10 -07:00
2007-07-26 11:35:19 -07:00
2007-02-20 17:11:55 +00:00
2007-07-19 10:04:43 -07:00
2007-07-19 10:04:43 -07:00
2007-07-29 17:09:29 -07:00
2007-07-17 10:23:10 -07:00
2007-07-16 09:05:47 -07:00
2007-02-12 09:48:30 -08:00
2007-07-21 17:49:16 -07:00
2007-07-17 10:23:10 -07:00
2007-07-16 09:05:46 -07:00
2007-07-10 17:51:13 -07:00
2006-12-08 08:28:59 -08:00
2007-08-22 19:52:46 -07:00
2007-05-08 11:15:05 -07:00
2007-07-16 09:05:47 -07:00
2006-12-20 16:37:48 +11:00
2007-10-01 07:52:23 -07:00