diff options
| author | Eric Dumazet <eric.dumazet@gmail.com> | 2010-05-17 22:35:36 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2010-08-02 10:29:19 -0700 |
| commit | a1899b1af296841f26afc39194d1857f963cbbac (patch) | |
| tree | b1b456f7555580f979d1226573e11410a9d9225c /drivers/rapidio/rio.c | |
| parent | efa4be3c2cb92b1d9d7d04ab91736cfc937a9764 (diff) | |
tcp: tcp_synack_options() fix
[ Upstream commit de213e5eedecdfb1b1eea7e6be28bc64cac5c078 ]
Commit 33ad798c924b4a (tcp: options clean up) introduced a problem
if MD5+SACK+timestamps were used in initial SYN message.
Some stacks (old linux for example) try to negotiate MD5+SACK+TSTAMP
sessions, but since 40 bytes of tcp options space are not enough to
store all the bits needed, we chose to disable timestamps in this case.
We send a SYN-ACK _without_ timestamp option, but socket has timestamps
enabled and all further outgoing messages contain a TS block, all with
the initial timestamp of the remote peer.
Fix is to really disable timestamps option for the whole session.
Reported-by: Bijay Singh <Bijay.Singh@guavus.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/rapidio/rio.c')
0 files changed, 0 insertions, 0 deletions