From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: netdev@vger.kernel.org
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
davem@davemloft.net, kuba@kernel.org,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: [PATCH net 0/4] mptcp: Fixes for 5.13
Date: Thu, 27 May 2021 16:31:36 -0700 [thread overview]
Message-ID: <20210527233140.182728-1-mathew.j.martineau@linux.intel.com> (raw)
These patches address two issues in MPTCP.
Patch 1 fixes a locking issue affecting MPTCP-level retransmissions.
Patches 2-4 improve handling of out-of-order packet arrival early in a
connection, so it falls back to TCP rather than forcing a
reset. Includes a selftest.
Paolo Abeni (4):
mptcp: fix sk_forward_memory corruption on retransmission
mptcp: always parse mptcp options for MPC reqsk
mptcp: do not reset MP_CAPABLE subflow on mapping errors
mptcp: update selftest for fallback due to OoO
net/mptcp/protocol.c | 16 +++-
net/mptcp/subflow.c | 79 ++++++++++---------
.../selftests/net/mptcp/mptcp_connect.sh | 13 ++-
3 files changed, 64 insertions(+), 44 deletions(-)
base-commit: fb91702b743dec78d6507c53a2dec8a8883f509d
--
2.31.1
next reply other threads:[~2021-05-27 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 23:31 Mat Martineau [this message]
2021-05-27 23:31 ` [PATCH net 1/4] mptcp: fix sk_forward_memory corruption on retransmission Mat Martineau
2021-05-27 23:31 ` [PATCH net 2/4] mptcp: always parse mptcp options for MPC reqsk Mat Martineau
2021-05-27 23:31 ` [PATCH net 3/4] mptcp: do not reset MP_CAPABLE subflow on mapping errors Mat Martineau
2021-05-27 23:31 ` [PATCH net 4/4] mptcp: update selftest for fallback due to OoO Mat Martineau
2021-05-28 21:00 ` [PATCH net 0/4] mptcp: Fixes for 5.13 patchwork-bot+netdevbpf
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=20210527233140.182728-1-mathew.j.martineau@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).