mptcp: add reset and fastclose option support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | tcp: make two mptcp helpers available to tcp stackinclude/ include/ net/ | +15 | 2 replies | |
| 2/5 | tcp: parse mptcp options contained in reset packetsinclude/ net/ net/ | +10 | 0 replies | |
| 3/5 | mptcp: add mptcp reset option supportinclude/ include/ net/ +5 more | +134 | 4 replies | |
| 4/5 | mptcp: parse and act on incoming FASTCLOSE optionnet/ net/ net/ | +52 | 0 replies | |
| 5/5 | mptcp: send fastclose if userspace closes socket with unread datanet/ net/ net/ | +67 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [MPTCP] [PATCH MPTCP 0/5] mptcp: add reset and fastclose option support
This series adds reset and fast close options.
Both need common infrastructure:
1. need to parse mptcp option in tcp reset packets, and making them available to the stack
2. ability to add mptcp option to tcp reset packets
First two patches move code around and add mptcp-callsite for option deciding from rst packets.
Patch 3 adds reset support (both decoding and adding them). Patch 4 adds the fastclose receive processing. Patch 5 sends a fastclose packet when userspace calls close() while there is unread data in the mptcp rx queue.
Patch 2) is not strictly need ATM, I could rework the series to remove it and only handle fastclose for the time being. Last patch could be removed as well so we only handle the rx case (there is nothing in RFC that says we must send fastclose).
Comments welcome.