From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v3 0/7] add fastclose testcases
Date: Tue, 15 Feb 2022 17:17:16 -0800 (PST) [thread overview]
Message-ID: <4267dfb9-224b-228a-83c0-6d2da77fd8e1@linux.intel.com> (raw)
In-Reply-To: <cover.1644923074.git.geliang.tang@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On Tue, 15 Feb 2022, Geliang Tang wrote:
> v3:
> - merge the squash-to patch ("Squash to "selftests: mptcp: add
> fastclose testcases v2") into v3.
> - add a new patch to check fastclose in mptcp_connect.sh
>
> base-commit: 9dff76d953f7a0fe2b27818f2aa93031c9a617cf
>
> v2:
> - merge the squash-to patch ("Squash to "selftests: mptcp: add the
> MP_RST mibs check") into v2.
> - update the commit logs.
>
> This patchset is related to issue #48 and issue #197. The two MP_RST
> patches are moved from the "add mp_fail testcases" series.
>
Hi Geliang -
The code changes and the squash-to patch look good in terms of code
review. When I run the 'mptcp_join.sh -z' test I get intermittent failures
with "fastclose test 2":
002 fastclose test 2 syn[ ok ] - synack[ ok ] - ack[ ok ]
ctx[ ok ] - fclzrx[fail] got 1 MP_FASTCLOSE[s] RX expected 2
rtx[ ok ] - rstrx [fail] got 1 MP_RST[s] RX expected 2 invert
(removed MIB dump)
I was able to reproduce while capturing, and the capture in the failed
test does have 2 MP_FASTCLOSE and 2 MP_RST. Maybe there's a timing issue
reading the MIBs?
I attached the pcaps, one for passing and one for failing.
-Mat
> Geliang Tang (7):
> mptcp: add the mibs for MP_FASTCLOSE
> selftests: mptcp: add the MP_FASTCLOSE mibs check
> mptcp: add the mibs for MP_RST
> selftests: mptcp: add the MP_RST mibs check
> selftests: mptcp: add extra_args in do_transfer
> selftests: mptcp: add fastclose testcases
> selftests: mptcp: fastclose check in mptcp_connect
>
> net/mptcp/mib.c | 4 +
> net/mptcp/mib.h | 4 +
> net/mptcp/options.c | 5 +
> .../selftests/net/mptcp/mptcp_connect.sh | 37 +++++
> .../testing/selftests/net/mptcp/mptcp_join.sh | 134 ++++++++++++++++--
> 5 files changed, 171 insertions(+), 13 deletions(-)
>
> --
> 2.34.1
--
Mat Martineau
Intel
[-- Attachment #2: Type: application/octet-stream, Size: 13231 bytes --]
next prev parent reply other threads:[~2022-02-16 1:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 11:12 [PATCH mptcp-next v3 0/7] add fastclose testcases Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 1/7] mptcp: add the mibs for MP_FASTCLOSE Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 2/7] selftests: mptcp: add the MP_FASTCLOSE mibs check Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 3/7] mptcp: add the mibs for MP_RST Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 4/7] selftests: mptcp: add the MP_RST mibs check Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 5/7] selftests: mptcp: add extra_args in do_transfer Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 6/7] selftests: mptcp: add fastclose testcases Geliang Tang
2022-02-15 11:12 ` [PATCH mptcp-next v3 7/7] selftests: mptcp: fastclose check in mptcp_connect Geliang Tang
2022-02-16 1:17 ` Mat Martineau [this message]
2022-02-18 7:16 ` [PATCH mptcp-next v3 0/7] add fastclose testcases Geliang Tang
2022-02-18 9:40 ` Geliang Tang
2022-02-19 0:02 ` 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=4267dfb9-224b-228a-83c0-6d2da77fd8e1@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=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.