Skip to content

RFC mptcp: add reset option support

Florian Westphal mptcp 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest4 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4net: tcp: drop unused function argument from mptcp_incoming_optionsinclude/net/mptcp.h net/ipv4/tcp_input.c net/mptcp/options.c+5 -81 reply
2/4tcp: move selected mptcp helpers to tcp.h/mptcp.hinclude/net/mptcp.h include/net/tcp.h net/mptcp/protocol.h+15 -110 replies
3/4mptcp: add mptcp reset option supportinclude/net/mptcp.h include/net/tcp.h net/ipv4/tcp_ipv4.c +5 more+134 -90 replies
4/4tcp: parse tcp options contained in reset packetsinclude/net/tcp.h net/ipv4/tcp_input.c net/ipv4/tcp_minisocks.c+10 -70 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [MPTCP] [RFC PATCH 0/4] mptcp: add reset option support

This series adds initial support for the RESET option. First patch is a minor cleanup, I would propose to pass this to net-next.

Second patch moves a few helpers around so they can be used from tcp core (needed to add mtpcp reset option to 'active resets', as those do not use the normal tcp output option path).

Third patch adds mptcp reset option, both for sending and receiving.

Last patch adds a call to the mptcp layer for inbound resets.

At this time, this is non-sensical, as nothing makes use of the rest-option hint.

The option/reason code would have to be propagated to the PM so it could use that for e.g. reconnect decisions.

We can discuss further steps in todays meeting.