MPTCP Linux Development
 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 0/3] add mp_fail testcases
Date: Tue, 25 Jan 2022 19:48:58 +0800	[thread overview]
Message-ID: <cover.1643110285.git.geliang.tang@suse.com> (raw)

The testcases v10 is unstable, it has two issues:

 - send too many infinite maps, the data translation was cease.
 - the infinite map may be lost, it wasn't received.

Add two squash-to patch to fix these issues, and make the testcases more
stable.

Geliang Tang (3):
  Squash to "mptcp: infinite mapping sending"
  Squash to "mptcp: infinite mapping receiving"
  selftests: mptcp: add mp_fail testcases

 net/mptcp/options.c                           |   2 +-
 net/mptcp/pm.c                                |   4 +-
 net/mptcp/protocol.h                          |  10 +-
 net/mptcp/subflow.c                           |   7 +-
 tools/testing/selftests/net/mptcp/config      |   5 +
 .../testing/selftests/net/mptcp/mptcp_join.sh | 148 +++++++++++++++---
 6 files changed, 153 insertions(+), 23 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-01-25 11:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 11:48 Geliang Tang [this message]
2022-01-25 11:48 ` [PATCH mptcp-next 1/3] Squash to "mptcp: infinite mapping sending" Geliang Tang
2022-01-26 23:58   ` Mat Martineau
2022-01-27  7:30     ` Geliang Tang
2022-01-25 11:49 ` [PATCH mptcp-next 2/3] Squash to "mptcp: infinite mapping receiving" Geliang Tang
2022-01-27  0:05   ` Mat Martineau
2022-01-25 11:49 ` [PATCH mptcp-next 3/3] selftests: mptcp: add mp_fail testcases Geliang Tang
2022-01-27  0:07   ` Mat Martineau
2022-01-28 17:04     ` Matthieu Baerts
2022-02-07  4:13       ` Geliang Tang
2022-02-07 10:32         ` Matthieu Baerts
2022-02-07 14:08           ` Geliang Tang
2022-02-08 12:26             ` Matthieu Baerts
2022-02-08 15:41               ` Geliang Tang
2022-02-08 16:24                 ` Matthieu Baerts
2022-02-08 19:40                   ` Matthieu Baerts
2022-02-09  6:23                     ` Geliang Tang

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.1643110285.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox