From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH mptcp-net v2 0/4] mptcp: fix races in add_addr handling
Date: Tue, 8 Feb 2022 20:06:14 +0100 [thread overview]
Message-ID: <cover.1644346664.git.pabeni@redhat.com> (raw)
the patches 1 && 2 fix actual races, even if the race addressed by
2/4 is not exposed by the self-tests, afaics.
patch 3 introduces some mibs to detect critical scenarios we can't
fix without major rework
patch 4 updates the self-test to be graceful in above cases.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/254
Paolo Abeni (4):
mptcp: fix race in overlapping signal events
mptcp: fix race in incoming ADD_ADDR option processing.
mptcp: add mibs counter for ignored incoming options
selftests: mptcp: more robust signal race test
net/mptcp/mib.c | 2 ++
net/mptcp/mib.h | 2 ++
net/mptcp/pm.c | 8 +++--
net/mptcp/pm_netlink.c | 29 +++++++++++++++----
.../testing/selftests/net/mptcp/mptcp_join.sh | 16 ++++++++--
5 files changed, 47 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-08 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:06 Paolo Abeni [this message]
2022-02-08 19:06 ` [PATCH mptcp-net v2 1/4] mptcp: fix race in overlapping signal events Paolo Abeni
2022-02-09 0:54 ` Mat Martineau
2022-02-09 8:54 ` Paolo Abeni
2022-02-09 9:29 ` Matthieu Baerts
2022-02-08 19:06 ` [PATCH mptcp-net v2 2/4] mptcp: fix race in incoming ADD_ADDR option processing Paolo Abeni
2022-02-08 21:25 ` Matthieu Baerts
2022-02-09 0:54 ` Mat Martineau
2022-02-09 8:49 ` Paolo Abeni
2022-02-09 9:32 ` Matthieu Baerts
2022-02-08 19:06 ` [PATCH mptcp-net v2 3/4] mptcp: add mibs counter for ignored incoming options Paolo Abeni
2022-02-08 19:06 ` [PATCH mptcp-net v2 4/4] selftests: mptcp: more robust signal race test Paolo Abeni
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.1644346664.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.