From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v5 mptcp-next 0/4] mptcp: more self-tests improvements
Date: Thu, 17 Feb 2022 22:44:10 +0100 [thread overview]
Message-ID: <cover.1645134065.git.pabeni@redhat.com> (raw)
This iteration tries to address the feedback from Mat on v4.
patch 1/4 is new and tries to address the problem behind issues/225 with
stricted RFC compliance
patch 2 and 3 clean-up endpoint management as per past discussion
patch 4 introduce new self-tests, as deserved the previous patch
Paolo Abeni (4):
mptcp: more careful RM_ADDR generation
mptcp: introduce implicit endpoints
mptcp: strict local address ID selection.
selftests: mptcp: add implicit endpoint test case
include/uapi/linux/mptcp.h | 1 +
net/mptcp/pm_netlink.c | 84 ++++++------
net/mptcp/protocol.c | 3 +
net/mptcp/protocol.h | 3 +-
net/mptcp/subflow.c | 67 ++++++++--
.../testing/selftests/net/mptcp/mptcp_join.sh | 121 +++++++++++++++++-
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 7 +
7 files changed, 234 insertions(+), 52 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-17 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 21:44 Paolo Abeni [this message]
2022-02-17 21:44 ` [PATCH v5 mptcp-next 1/4] mptcp: more careful RM_ADDR generation Paolo Abeni
2022-02-17 21:44 ` [PATCH v5 mptcp-next 2/4] mptcp: introduce implicit endpoints Paolo Abeni
2022-02-17 21:44 ` [PATCH v5 mptcp-next 3/4] mptcp: strict local address ID selection Paolo Abeni
2022-02-17 21:44 ` [PATCH v5 mptcp-next 4/4] selftests: mptcp: add implicit endpoint test case Paolo Abeni
2022-02-18 1:35 ` [PATCH v5 mptcp-next 0/4] mptcp: more self-tests improvements Mat Martineau
2022-02-18 9:02 ` Paolo Abeni
2022-02-18 20:33 ` Mat Martineau
2022-02-21 9:16 ` Paolo Abeni
2022-02-19 17:15 ` 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.1645134065.git.pabeni@redhat.com \
--to=pabeni@redhat.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.