From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v3 0/3] MP_FAIL echo and retrans
Date: Wed, 9 Mar 2022 20:33:56 +0800 [thread overview]
Message-ID: <cover.1646829006.git.geliang.tang@suse.com> (raw)
v3:
- use msk->sk_timer and a msk->flags bit.
- use READ_ONCE/WRITE_ONCE for subflow->mp_fail_response_expect.
- update selftest.
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
mptcp: reset subflow when MP_FAIL doesn't respond
selftests: mptcp: check MP_FAIL response mibs
net/mptcp/pm.c | 11 ++++--
net/mptcp/protocol.c | 21 +++++++++++
net/mptcp/protocol.h | 2 ++
net/mptcp/subflow.c | 4 +++
.../testing/selftests/net/mptcp/mptcp_join.sh | 36 ++++++++++++++++---
5 files changed, 67 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-09 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:33 Geliang Tang [this message]
2022-03-09 12:33 ` [PATCH mptcp-next v3 1/3] mptcp: add MP_FAIL response support Geliang Tang
2022-03-09 12:33 ` [PATCH mptcp-next v3 2/3] mptcp: reset subflow when MP_FAIL doesn't respond Geliang Tang
2022-03-10 0:01 ` Mat Martineau
2022-03-09 12:33 ` [PATCH mptcp-next v3 3/3] selftests: mptcp: check MP_FAIL response mibs Geliang Tang
2022-03-09 14:30 ` selftests: mptcp: check MP_FAIL response mibs: Tests Results MPTCP CI
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.1646829006.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.