diff options
| author | Douglas Caetano dos Santos <douglascs@taghos.com.br> | 2017-05-26 19:28:00 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-05-31 18:28:59 +0200 |
| commit | 15e5651525c2e580a523568ed207e4a3fb11cc33 (patch) | |
| tree | 84ce905be24070575b395394419c2841b10a5431 /net/vmw_vsock/af_vsock_tap.c | |
| parent | Merge branch 'mlx4-mlx5-MAINTAINERS-update' (diff) | |
| download | linux-15e5651525c2e580a523568ed207e4a3fb11cc33.tar.xz linux-15e5651525c2e580a523568ed207e4a3fb11cc33.zip | |
tcp: reinitialize MTU probing when setting MSS in a TCP repair
MTU probing initialization occurred only at connect() and at SYN or
SYN-ACK reception, but the former sets MSS to either the default or the
user set value (through TCP_MAXSEG sockopt) and the latter never happens
with repaired sockets.
The result was that, with MTU probing enabled and unless TCP_MAXSEG
sockopt was used before connect(), probing would be stuck at
tcp_base_mss value until tcp_probe_interval seconds have passed.
Signed-off-by: Douglas Caetano dos Santos <douglascs@taghos.com.br>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/vmw_vsock/af_vsock_tap.c')
0 files changed, 0 insertions, 0 deletions