From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [RFC v2 PATCH 0/2] mptcp: fix deadlock in mptcp{,6}_release
Date: Wed, 03 Mar 2021 19:43:37 +0100 [thread overview]
Message-ID: <cover.1614796802.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
This address the issue the easy way: removing the bugged features
(a lot of setsockopt including all mcast related).
As suggested by Mat(s) this switch to a whitelist. Assembling the
whilelist itself is quite complex/tedious/errorprone so still RFC.
Please have a look at 1/2 for the details
Paolo Abeni (2):
mptcp: only admit explicitly supported sockopt
mptcp: revert "mptcp: provide subflow aware release function"$ ....$
net/mptcp/protocol.c | 270 ++++++++++++++++++++++++++++++++++---------
1 file changed, 217 insertions(+), 53 deletions(-)
--
2.26.2
reply other threads:[~2021-03-03 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1614796802.git.pabeni@redhat.com \
--to=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