From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH mptcp-net 0/5] mptcp: mp_fail related fixes
Date: Wed, 15 Jun 2022 11:16:11 +0200 [thread overview]
Message-ID: <cover.1655283387.git.pabeni@redhat.com> (raw)
While cooking a follow-up for "mptcp: invoke MP_FAIL response when
needed" I stumbled upon a few other MP_FAIL related issues hit my
the self-tests while mangling the above.
All the patches for for the -net tree, and should be applied in-order
around to the squashed-to patch.
Note: with this series I still observe sporardic failures (once every
~200 runs) of tests 95. Given the low frequency here I did not investigate
them yet...
Paolo Abeni (5):
mptcp: fix error mibs accounting
mptcp: introduce MAPPING_BAD_CSUM
Squash-to: "mptcp: invoke MP_FAIL response when needed"
mptcp: fix shutdown vs fallback race
mptcp: consistent map handling on failure
net/mptcp/options.c | 8 +++---
net/mptcp/pm.c | 5 ++--
net/mptcp/protocol.c | 56 ++++++++++++++++++++++++++++++++-------
net/mptcp/protocol.h | 23 ++++++++++++----
net/mptcp/subflow.c | 63 ++++++++++++++++++++++++++++----------------
5 files changed, 111 insertions(+), 44 deletions(-)
--
2.35.3
next reply other threads:[~2022-06-15 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 9:16 Paolo Abeni [this message]
2022-06-15 9:16 ` [PATCH mptcp-net 1/5] mptcp: fix error mibs accounting Paolo Abeni
2022-06-15 9:16 ` [PATCH mptcp-net 2/5] mptcp: introduce MAPPING_BAD_CSUM Paolo Abeni
2022-06-15 9:16 ` [PATCH mptcp-net 3/5] Squash-to: "mptcp: invoke MP_FAIL response when needed" Paolo Abeni
2022-06-15 11:41 ` Paolo Abeni
2022-06-15 9:16 ` [PATCH mptcp-net 4/5] mptcp: fix shutdown vs fallback race Paolo Abeni
2022-06-15 9:16 ` [PATCH mptcp-net 5/5] mptcp: consistent map handling on failure Paolo Abeni
2022-06-15 11:00 ` mptcp: consistent map handling on failure: Tests Results MPTCP CI
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.1655283387.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox