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, pabeni@redhat.com,
edumazet@google.com, fw@strlen.de, kishen.maloor@intel.com,
dcaratti@redhat.com, matthieu.baerts@tessares.net,
mptcp@lists.linux.dev, stable@vger.kernel.org
Subject: [PATCH net 0/4] mptcp: Fix IPv6 reqsk ops and some netlink error codes
Date: Fri, 9 Dec 2022 16:28:06 -0800 [thread overview]
Message-ID: <20221210002810.289674-1-mathew.j.martineau@linux.intel.com> (raw)
Patch 1 adds some missing error status values for MPTCP path management
netlink commands with invalid attributes.
Patches 2-4 make IPv6 subflows use the correct request_sock_ops
structure and IPv6-specific destructor. The first patch in this group is
a prerequisite change that simplifies the last two patches.
Matthieu Baerts (3):
mptcp: remove MPTCP 'ifdef' in TCP SYN cookies
mptcp: dedicated request sock for subflow in v6
mptcp: use proper req destructor for IPv6
Wei Yongjun (1):
mptcp: netlink: fix some error return code
include/net/mptcp.h | 12 ++++++--
net/ipv4/syncookies.c | 7 ++---
net/mptcp/pm_userspace.c | 4 +++
net/mptcp/subflow.c | 61 +++++++++++++++++++++++++++++++++-------
4 files changed, 68 insertions(+), 16 deletions(-)
base-commit: 01de1123322e4fe1bbd0fcdf0982511b55519c03
--
2.38.1
next reply other threads:[~2022-12-10 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 0:28 Mat Martineau [this message]
2022-12-10 0:28 ` [PATCH net 1/4] mptcp: netlink: fix some error return code Mat Martineau
2022-12-10 0:28 ` [PATCH net 2/4] mptcp: remove MPTCP 'ifdef' in TCP SYN cookies Mat Martineau
2022-12-10 0:28 ` [PATCH net 3/4] mptcp: dedicated request sock for subflow in v6 Mat Martineau
2022-12-10 0:28 ` [PATCH net 4/4] mptcp: use proper req destructor for IPv6 Mat Martineau
2022-12-12 21:20 ` [PATCH net 0/4] mptcp: Fix IPv6 reqsk ops and some netlink error codes 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=20221210002810.289674-1-mathew.j.martineau@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kishen.maloor@intel.com \
--cc=kuba@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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