Ipv6 TCP timewait recycling support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest7 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | inetpeer: Kill use of inet_peer_address_t typedef.include/ net/ | +10 | 0 replies | |
| 2/7 | inetpeer: Fix incorrect comment about inetpeer struct size.include/ | +0 | 0 replies | |
| 3/7 | timewait_sock: Create and use getpeer op.include/ include/ net/ +2 more | +63 | 0 replies | |
| 4/7 | ipv6: Add rt6_get_peer() helper.include/ | +9 | 0 replies | |
| 5/7 | ipv6: Create inet6_csk_route_req().include/ net/ | +35 | 0 replies | |
| 6/7 | tcp: Add timewait recycling bits to ipv6 connect code.net/ net/ | +77 | 0 replies | |
| 7/7 | tcp: Implement ipv6 ->get_peer() and ->tw_get_peer().net/ | +18 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/7] Ipv6 TCP timewait recycling support
First we start with two simple cleanups, un-typedef'ification and a comment fixup.
Then we add the infrastructure to allow the tcp_minisocks.c timewait recycling code able to be generic and use various ->ops
Sadly, the ipv6 timewait ops are used even for v4-mapped addresses so we need a special check in the ipv6 timewait getpeer implementation. This is similar to the situation we have in tcp_v6_hash().
Doing these changes also pointed out that our listening socket incoming connection policy in the non-syncookies case as being handled differently for ipv4 vs. ipv6. This has been rectified. The issue is that for ipv4 we were reserving the final 1/4 of the backlog queue to validated destinations.
In the final patch we throw the switch and implement the two getpeer operations for ipv6, which fully enables timewait recyling for ipv6.