[PATCH mptcp-net/next v3 00/11] mptcp: add support for mixed v4/v6

Matthieu Baerts posted 11 patches 1 year, 3 months ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/20221227182057.2288816-1-matthieu.baerts@tessares.net
Maintainers: Mat Martineau <mathew.j.martineau@linux.intel.com>, Matthieu Baerts <matthieu.baerts@tessares.net>, "David S. Miller" <davem@davemloft.net>, Eric Dumazet <edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>, Florian Westphal <fw@strlen.de>, Kishen Maloor <kishen.maloor@intel.com>
There is a newer version of this series
net/mptcp/pm.c                                |  25 +++
net/mptcp/pm_netlink.c                        |  55 +++---
net/mptcp/pm_userspace.c                      |  14 +-
net/mptcp/protocol.c                          |   2 +-
net/mptcp/protocol.h                          |   6 +-
net/mptcp/sockopt.c                           |   1 +
net/mptcp/subflow.c                           |   9 +-
.../testing/selftests/net/mptcp/mptcp_join.sh |  53 +++++-
.../selftests/net/mptcp/userspace_pm.sh       | 164 +++++++++++++-----
9 files changed, 244 insertions(+), 85 deletions(-)
[PATCH mptcp-net/next v3 00/11] mptcp: add support for mixed v4/v6
Posted by Matthieu Baerts 1 year, 3 months ago
This is a v3 of Paolo's series with the same name with some
modifications and additional patches.

This series can be split in 2 parts: the 3 first patches are for -net
while the rest is for net-next.

Patch 1 let the userspace PM selects the proper family to avoid creating
subflows with wrong source and/or destination addresses because the
family is not the expected one.

Patch 2 makes sure the userspace PM doesn't allow the userspace to
create subflows for a family that is not allowed.

The core MPTCP implementation is just a few bits of properly supporting
a mix of v4 and v6 subflows, we just need to allow specifying the
subflow family explicitly (patch 1) and remove artificial constraints in
the in-kernel PM currently enforcing no mixed subflow in place (patch
4).

Patch 5 makes sure the sk_ipv6only attribute is also propagated to
subflows, just in case the PM doesn't respect it.

Some selftests have also been added for the userspace PM (patch 3) and
the in-kernel PM (patch 6).

Patches 7 and 8 are just some cleanups in the userspace PM, not related
to the rest but I saw them when modifying the file.

Patches 9 to 11 improve the messages printed by the userspace PM,
especially in case of error during the validation.

Matthieu Baerts (8):
  mptcp: netlink: respect v4/v6-only sockets
  selftests: mptcp: userspace: validate v4-v6 subflows mix
  mptcp: propagate sk_ipv6only to subflows
  mptcp: remove assigned but unused value
  mptcp: userspace pm: use a single point of exit
  selftests: mptcp: userspace: print titles
  selftests: mptcp: userspace: refactor asserts
  selftests: mptcp: userspace: print error details if any

Paolo Abeni (3):
  mptcp: explicitly specify sock family at subflow creation time
  mptcp: let the in-kernel PM use mixed IPv4 and IPv6 addresses
  selftests: mptcp: add test-cases for mixed v4/v6 subflows

 net/mptcp/pm.c                                |  25 +++
 net/mptcp/pm_netlink.c                        |  55 +++---
 net/mptcp/pm_userspace.c                      |  14 +-
 net/mptcp/protocol.c                          |   2 +-
 net/mptcp/protocol.h                          |   6 +-
 net/mptcp/sockopt.c                           |   1 +
 net/mptcp/subflow.c                           |   9 +-
 .../testing/selftests/net/mptcp/mptcp_join.sh |  53 +++++-
 .../selftests/net/mptcp/userspace_pm.sh       | 164 +++++++++++++-----
 9 files changed, 244 insertions(+), 85 deletions(-)


base-commit: fe84ec2a445f2ec26dc0484538f2175945b43822
--
2.37.2