MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH v6 mptcp-next 0/9] ADD_ADDR: ports support
Date: Wed, 25 Nov 2020 11:01:07 +0800	[thread overview]
Message-ID: <cover.1606272852.git.geliangtang@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]

v6:
 - create and bind the listening socket in mptcp_nl_cmd_add_addr.
 - drop the patch "mptcp: add port number listened in kernel check" in
   v5.

v5:
 - use the per netns listening socket.
 - First 8 patches in v4 had been merged to the export branch, drop them
   from this patchset.

v4:
 - hold msk->pm.lock in mptcp_pm_sport_in_anno_list.
 - Merge the patchset 'Squash to "ADD_ADDR: ports support v3"' into v4.

v3:
 - add two new patches, 8 and 11
 - add more IS_ENABLED(CONFIG_MPTCP_IPV6) in patch 2
 - define TCPOLEN_MPTCP_ADD_ADDR_HMAC in patch 4
 - add flags check in patch 10
 - update the testcases

v2:
 - change mptcp_out_options's port field in CPU bype order.
 - keep mptcp_options_received's port field in CPU bype order.
 - add two new patches to simplify ADD_ADDR suboption writing.
 - update mptcp_add_addr_len helper use adding up size.
 - add more commit messages.

v1:
 This series is the first version of ADD_ADDR ports support. I have solved
 the listener problem which I mentioned at the meeting on 15th of October
 by adding a new listening socket from the userspace (see patch 8). Up to
 now this patchset works well.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/54

Geliang Tang (9):
  mptcp: create the listening socket for new port
  mptcp: set the listening socket's subflow
  mptcp: release the listening socket
  mptcp: add port number check for MP_JOIN
  mptcp: add port number announced check
  mptcp: deal with MPTCP_PM_ADDR_ATTR_PORT in PM netlink
  selftests: mptcp: add port argument for pm_nl_ctl
  mptcp: add the mibs for ADD_ADDR with port
  selftests: mptcp: add testcases for ADD_ADDR with port

 net/mptcp/mib.c                               |   4 +
 net/mptcp/mib.h                               |   4 +
 net/mptcp/options.c                           |   4 +
 net/mptcp/pm_netlink.c                        |  91 +++++++++++++-
 net/mptcp/protocol.h                          |   5 +
 net/mptcp/subflow.c                           |  80 +++++++++++-
 .../testing/selftests/net/mptcp/mptcp_join.sh | 114 +++++++++++++++++-
 tools/testing/selftests/net/mptcp/pm_nl_ctl.c |  24 +++-
 8 files changed, 315 insertions(+), 11 deletions(-)

-- 
2.26.2

                 reply	other threads:[~2020-11-25  3:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cover.1606272852.git.geliangtang@gmail.com \
    --to=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