All of lore.kernel.org
 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/5] remove id 0 address
Date: Thu, 04 Mar 2021 17:33:31 +0800	[thread overview]
Message-ID: <cover.1614849685.git.geliangtang@gmail.com> (raw)

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

v6:
 - add addr argument for del_addr.
 - tag: export/20210226T185626
 - need to apply the squash-to patchset "avoid passing rm_list as a struct"
or the single patch "avoid passing rm_list as a struct" in v5 first.

v5:
 - add patch 1 "avoid passing rm_list as a struct".
 - re-use MPTCP_MIB_RMADDR/MPTCP_MIB_RMSUBFLOW in patch 3.
 - use (id == 0) instead of (!id) in patch 4.

v4:
 - add new function mptcp_nl_remove_id_zero_address.
 - add new testcases.

v3:
 - print subflow ids in patch 1;
 - add the initial subflow's ids check in patch 2;
 - update the test in patch 3;

v2:
 - drop __mptcp_wr_shutdown in v1.

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

Geliang Tang (5):
  mptcp: remove all subflows involving id 0 address
  mptcp: unify RM_ADDR and RM_SUBFLOW receiving
  mptcp: remove id 0 address
  selftests: mptcp: add addr argument for del_addr
  selftests: mptcp: remove id 0 address testcases

 net/mptcp/pm_netlink.c                        | 127 ++++++++++--------
 .../testing/selftests/net/mptcp/mptcp_join.sh |  35 ++++-
 tools/testing/selftests/net/mptcp/pm_nl_ctl.c |  33 ++++-
 3 files changed, 137 insertions(+), 58 deletions(-)

-- 
2.29.2

                 reply	other threads:[~2021-03-04  9:33 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.1614849685.git.geliangtang@gmail.com \
    --to=unknown@example.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.