From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v4 0/5] add mp_fail testcases
Date: Wed, 9 Feb 2022 16:57:36 +0800 [thread overview]
Message-ID: <cover.1644396927.git.geliang.tang@suse.com> (raw)
v4:
- add the mibs for MP_RST
- patch 4 "selftests: mptcp: add MP_RST mibs check" uses the variable
$nr_blank, so it depends on the commit "selftests: mptcp: adjust output
alignment for more tests".
v3:
- check the exit code of iptables.
- add ip6tables support for reset_with_fail too.
- add the null check for $packets
- rename nr_mp_fail to pedit_action and get_nr_mp_fail to
pedit_action_happened
This is v12 of the mp_fail testcases with Matt's changes. It works well
and it's very stable.
Geliang Tang (5):
Squash to "mptcp: infinite mapping receiving"
Squash to "selftests: mptcp: add infinite map mibs check"
mptcp: add mibs for MP_RST
selftests: mptcp: add MP_RST mibs check
selftests: mptcp: add mp_fail testcases
net/mptcp/mib.c | 2 +
net/mptcp/mib.h | 2 +
net/mptcp/options.c | 2 +
net/mptcp/subflow.c | 1 +
tools/testing/selftests/net/mptcp/config | 8 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 217 +++++++++++++++---
6 files changed, 204 insertions(+), 28 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-09 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 8:57 Geliang Tang [this message]
2022-02-09 8:57 ` [PATCH mptcp-next v4 1/5] Squash to "mptcp: infinite mapping receiving" Geliang Tang
2022-02-09 8:57 ` [PATCH mptcp-next v4 2/5] Squash to "selftests: mptcp: add infinite map mibs check" Geliang Tang
2022-02-09 8:57 ` [PATCH mptcp-next v4 3/5] mptcp: add mibs for MP_RST Geliang Tang
2022-02-09 8:57 ` [PATCH mptcp-next v4 4/5] selftests: mptcp: add MP_RST mibs check Geliang Tang
2022-02-09 8:57 ` [PATCH mptcp-next v4 5/5] selftests: mptcp: add mp_fail testcases Geliang Tang
2022-02-09 9:23 ` Matthieu Baerts
2022-02-09 10:55 ` Geliang Tang
2022-02-09 11:13 ` Matthieu Baerts
2022-02-09 13:52 ` 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.1644396927.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.