All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/3] MP_FAIL echo and retrans
Date: Mon,  7 Mar 2022 21:09:14 +0800	[thread overview]
Message-ID: <cover.1646657963.git.geliang.tang@suse.com> (raw)

v2:
 - don't clear mp_fail_response_expect flag.
 - add a helper mp_fail_response_expect_subflow to get the subflow,
   instead of using msk->first.
 - add locks as Mat suggested.
 - add a selftest.

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

Geliang Tang (3):
  mptcp: add MP_FAIL response support
  selftests: mptcp: check MP_FAIL response mibs
  mptcp: reset the subflow when MP_FAIL is lost

 net/mptcp/pm.c                                | 14 ++++-
 net/mptcp/protocol.c                          | 63 ++++++++++++++++++-
 net/mptcp/protocol.h                          |  2 +
 net/mptcp/subflow.c                           |  3 +
 .../testing/selftests/net/mptcp/mptcp_join.sh | 19 +++++-
 5 files changed, 94 insertions(+), 7 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-03-07 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 13:09 Geliang Tang [this message]
2022-03-07 13:09 ` [PATCH mptcp-next v2 1/3] mptcp: add MP_FAIL response support Geliang Tang
2022-03-07 13:09 ` [PATCH mptcp-next v2 2/3] selftests: mptcp: check MP_FAIL response mibs Geliang Tang
2022-03-07 13:09 ` [PATCH mptcp-next v2 3/3] mptcp: reset the subflow when MP_FAIL is lost Geliang Tang
2022-03-07 14:32   ` mptcp: reset the subflow when MP_FAIL is lost: Tests Results MPTCP CI
2022-03-09  1:02   ` [PATCH mptcp-next v2 3/3] mptcp: reset the subflow when MP_FAIL is lost Mat Martineau
2022-03-09  1:06     ` Mat Martineau

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.1646657963.git.geliang.tang@suse.com \
    --to=geliang.tang@suse.com \
    --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 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.