From: Geliang Tang <geliang.tang@linux.dev>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@linux.dev>
Subject: [PATCH mptcp-next v5 0/3] add MPTCP_MIB_CURRESTAB
Date: Wed, 13 Dec 2023 13:56:36 +0800 [thread overview]
Message-ID: <cover.1702446832.git.geliang.tang@linux.dev> (raw)
v5:
- merge first three patches into one as Paolo suggested.
- drop "EXPORT_SYMBOL_GPL(mptcp_set_state);" as Paolo suggested.
v4:
- rebased.
v3:
- add mptcp_set_state helper
v2:
- use ftrace_regs_get_argument instead of regs_get_kernel_argument to
fix build warnings reported kernel test robot.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/460
Geliang Tang (3):
mptcp: add mptcp_set_state
mptcp: use mptcp_set_state
selftests: mptcp: check CURRESTAB counters
net/mptcp/mib.c | 1 +
net/mptcp/mib.h | 8 +++
net/mptcp/pm_netlink.c | 3 +
net/mptcp/protocol.c | 56 ++++++++++++-------
net/mptcp/protocol.h | 1 +
net/mptcp/subflow.c | 2 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 45 +++++++++++++--
7 files changed, 91 insertions(+), 25 deletions(-)
--
2.35.3
next reply other threads:[~2023-12-13 5:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 5:56 Geliang Tang [this message]
2023-12-13 5:56 ` [PATCH mptcp-next v5 1/3] mptcp: add mptcp_set_state Geliang Tang
2023-12-13 5:56 ` [PATCH mptcp-next v5 2/3] mptcp: use mptcp_set_state Geliang Tang
2023-12-13 11:25 ` Matthieu Baerts
2023-12-15 16:30 ` Paolo Abeni
2023-12-18 15:56 ` Matthieu Baerts
2023-12-13 5:56 ` [PATCH mptcp-next v5 3/3] selftests: mptcp: check CURRESTAB counters Geliang Tang
2023-12-13 7:12 ` selftests: mptcp: check CURRESTAB counters: Tests Results MPTCP CI
2023-12-13 10:26 ` MPTCP CI
2023-12-13 11:43 ` [PATCH mptcp-next v5 3/3] selftests: mptcp: check CURRESTAB counters Matthieu Baerts
2023-12-13 9:15 ` [PATCH mptcp-next v5 0/3] add MPTCP_MIB_CURRESTAB Paolo Abeni
2023-12-13 11:51 ` 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.1702446832.git.geliang.tang@linux.dev \
--to=geliang.tang@linux.dev \
--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