From: Gang Yan <yangang@kylinos.cn>
To: mptcp@lists.linux.dev
Cc: Gang Yan <yangang@kylinos.cn>
Subject: [mptcp-next v3 0/2] selftests: mptcp: add tests for increasing
Date: Fri, 21 Feb 2025 13:34:17 +0800 [thread overview]
Message-ID: <cover.1740115494.git.yangang@kylinos.cn> (raw)
These patches provide a method to verify the 'mptcp_diag_dump_one'
function, and the new tool 'mptcp_diag' can get the specific mptcp_info
through multi msks.
Gang Yan (2):
selftests: mptcp: Add a tool to get specific msk_info
selftests: mptcp: add a test for mptcp_diag_dump_one
tools/testing/selftests/net/mptcp/Makefile | 2 +-
tools/testing/selftests/net/mptcp/diag.sh | 27 ++
.../testing/selftests/net/mptcp/mptcp_diag.c | 258 ++++++++++++++++++
3 files changed, 286 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/net/mptcp/mptcp_diag.c
--
2.25.1
next reply other threads:[~2025-02-21 5:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 5:34 Gang Yan [this message]
2025-02-21 5:34 ` [mptcp-next v3 1/2] selftests: mptcp: Add a tool to get specific msk_info Gang Yan
2025-02-21 11:55 ` Matthieu Baerts
2025-02-21 5:34 ` [mptcp-next v3 2/2] selftests: mptcp: add a test for mptcp_diag_dump_one Gang Yan
2025-02-21 11:55 ` Matthieu Baerts
2025-02-21 6:41 ` [mptcp-next v3 0/2] selftests: mptcp: add tests for increasing MPTCP CI
2025-02-21 11:54 ` Matthieu Baerts
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.1740115494.git.yangang@kylinos.cn \
--to=yangang@kylinos.cn \
--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