summaryrefslogtreecommitdiffstats
path: root/net/tipc
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2013-02-13 13:22:24 -0500
committerDavid S. Miller <davem@davemloft.net>2013-02-13 13:22:24 -0500
commitb8fa4100350432504df438014e2e5e9c1bbb6325 (patch)
tree0fc416746eeca68bbba228958636dd919fc3785f /net/tipc
parentd0023f820e003857248d14f2213ac3930283f16c (diff)
parentee684b6f2830047d19877e5547989740f18b1a5d (diff)
downloadlinux-b8fa4100350432504df438014e2e5e9c1bbb6325.tar.gz
linux-b8fa4100350432504df438014e2e5e9c1bbb6325.tar.bz2
linux-b8fa4100350432504df438014e2e5e9c1bbb6325.zip
Merge branch 'tcp_tsoffset'
Andrey Vagin says: ==================== If a TCP socket will get live-migrated from one box to another the timestamps (which are typically ON) will get screwed up -- the new kernel will generate TS values that has nothing to do with what they were on dump. The solution is to yet again fix the kernel and put a "timestamp offset" on a socket. A socket offset is added in places where externally visible tcp timestamp option is parsed/initialized. Connections in the SYN_RECV state are not supported, global tcp_time_stamp is used for them, because repair mode doesn't support this state. In a future it can be implemented by the similar way as for TIME_WAIT sockets. For time-wait sockets offset is inhereted by a proper tcp_sock. A per-socket offset can be set only for sockets in repair mode. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc')
0 files changed, 0 insertions, 0 deletions