MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net/next v5 00/12] mptcp: add support for mixed v4/v6
Date: Thu, 5 Jan 2023 17:15:02 -0800 (PST)	[thread overview]
Message-ID: <1d6a5e49-dd47-0c1a-c566-825e3da7e75b@linux.intel.com> (raw)
In-Reply-To: <20230104171526.1416746-1-matthieu.baerts@tessares.net>

On Wed, 4 Jan 2023, Matthieu Baerts wrote:

> This is a v5 of Paolo's series with the same name but with some
> modifications and additional patches.
>
> ChangeLog:
>  - v3 -> v4:
>    - Fix a compilation error without CONFIG_MPTCP_IPV6 in patch 4/12.
>    - Add a title for the cleanup part in patch 9/12
>    - Add the patch 12/12 to avoid "read" errors
>  - v4 -> v5:
>    - Fix typo in patch 2/12 (Mat)
>    - More details in the commit message of patch 2/12 (Mat)
>    - Rebased on top of the latest export branch
>
> This series can be split in 2 parts: the 3 first patches are for -net
> while the rest is for net-next. Patches for net-next depends on patches
> for -net, that's why everything is being sent together.
>
> Patch 1 lets 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 1-8 look good for further testing in the export (and export-net) 
branches:

Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>



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

I have a very minor formatting comment on patch 9 (separate reply)


- Mat


> Matthieu Baerts (9):
>  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
>  selftests: mptcp: userspace: avoid read errors
>
> 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                        |  58 ++---
> 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       | 200 ++++++++++++------
> 9 files changed, 262 insertions(+), 106 deletions(-)
>
>
> base-commit: 0e6e165b9b9b5ea418067cfac1e861892ee7e12c
> -- 
> 2.37.2
>
>
>

--
Mat Martineau
Intel

  parent reply	other threads:[~2023-01-06  1:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 17:15 [PATCH mptcp-net/next v5 00/12] mptcp: add support for mixed v4/v6 Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-net v5 01/12] mptcp: explicitly specify sock family at subflow creation time Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-net v5 02/12] mptcp: netlink: respect v4/v6-only sockets Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-net v5 03/12] selftests: mptcp: userspace: validate v4-v6 subflows mix Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 04/12] mptcp: let the in-kernel PM use mixed IPv4 and IPv6 addresses Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 05/12] mptcp: propagate sk_ipv6only to subflows Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 06/12] selftests: mptcp: add test-cases for mixed v4/v6 subflows Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 07/12] mptcp: remove assigned but unused value Matthieu Baerts
2023-01-10  9:20   ` Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 08/12] mptcp: userspace pm: use a single point of exit Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 09/12] selftests: mptcp: userspace: print titles Matthieu Baerts
2023-01-06  1:19   ` Mat Martineau
2023-01-06  6:34     ` Matthieu Baerts
2023-01-06 16:34       ` Mat Martineau
2023-01-04 17:15 ` [PATCH mptcp-next v5 10/12] selftests: mptcp: userspace: refactor asserts Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 11/12] selftests: mptcp: userspace: print error details if any Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 12/12] selftests: mptcp: userspace: avoid read errors Matthieu Baerts
2023-01-05  8:32   ` selftests: mptcp: userspace: avoid read errors: Tests Results MPTCP CI
2023-01-06  2:39   ` MPTCP CI
2023-01-06 17:39   ` MPTCP CI
2023-01-06  1:15 ` Mat Martineau [this message]
2023-01-09 17:04   ` [PATCH mptcp-net/next v5 00/12] mptcp: add support for mixed v4/v6 Matthieu Baerts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1d6a5e49-dd47-0c1a-c566-825e3da7e75b@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox