tcp: fix TCP_MAXSEG for established IPv6 passive sockets
authorNeal Cardwell <ncardwell@google.com>
Sun, 22 Apr 2012 09:45:47 +0000 (09:45 +0000)
committerDavid S. Miller <davem@davemloft.net>
Sun, 22 Apr 2012 21:09:35 +0000 (17:09 -0400)
commitd135c522f1234f62e81be29cebdf59e9955139ad
tree7e151f3995d6a30499c2bec2c07b2bf68754788e
parent163faf31778e536ac6125bc8b14f4667adc910e9
tcp: fix TCP_MAXSEG for established IPv6 passive sockets

Commit f5fff5d forgot to fix TCP_MAXSEG behavior IPv6 sockets, so IPv6
TCP server sockets that used TCP_MAXSEG would find that the advmss of
child sockets would be incorrect. This commit mirrors the advmss logic
from tcp_v4_syn_recv_sock in tcp_v6_syn_recv_sock. Eventually this
logic should probably be shared between IPv4 and IPv6, but this at
least fixes this issue.

Signed-off-by: Neal Cardwell <ncardwell@google.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv6/tcp_ipv6.c