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 v4 mptcp-next 0/2] move to next addr and testcases
Date: Thu, 18 Feb 2021 16:22:14 +0800	[thread overview]
Message-ID: <cover.1613635984.git.geliangtang@gmail.com> (raw)

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

v4:
 - use lookup_anno_list_by_saddr instead of lookup_subflow_by_saddr.
 - use MPTCP_PM_SUBFLOW_ESTABLISHED instead of MPTCP_PM_ESTABLISHED.

v3:
 - drop MPTCP_PM_NEXT_ADDR, use MPTCP_PM_ESTABLISHED instead.
 - hold the msk lock in mptcp_pm_add_addr_echoed.
 - tag: export/20210209T062213

v2:
 - add patch 2 and 3 for removing testcases.
 - tag: export/20210207T062839.

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

Geliang Tang (2):
  mptcp: move to next addr when subflow creation fail
  selftests: mptcp: signal addresses testcases

 net/mptcp/options.c                           |  1 +
 net/mptcp/pm.c                                | 15 +++++
 net/mptcp/pm_netlink.c                        |  2 +-
 net/mptcp/protocol.h                          |  5 ++
 .../testing/selftests/net/mptcp/mptcp_join.sh | 58 +++++++++++++++++++
 5 files changed, 80 insertions(+), 1 deletion(-)

-- 
2.29.2

                 reply	other threads:[~2021-02-18  8:22 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.1613635984.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