From: Andrey Vagin <[email protected]> Date: Mon, 11 Feb 2013 19:50:16 +0400
> 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. Series applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
