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, mptcp@lists.01.org,
matthieu.baerts@tessares.net
Subject: [PATCH net-next 0/8] mptcp: Add genl events for connection info
Date: Fri, 12 Feb 2021 15:59:53 -0800 [thread overview]
Message-ID: <20210213000001.379332-1-mathew.j.martineau@linux.intel.com> (raw)
This series from the MPTCP tree adds genl multicast events that are
important for implementing a userspace path manager. In MPTCP, a path
manager is responsible for adding or removing additional subflows on
each MPTCP connection. The in-kernel path manager (already part of the
kernel) is a better fit for many server use cases, but the additional
flexibility of userspace path managers is often useful for client
devices.
Patches 1, 2, 4, 5, and 6 do some refactoring to streamline the netlink
event implementation in the final patch.
Patch 3 improves the timeliness of subflow destruction to ensure the
'subflow closed' event will be sent soon enough.
Patch 7 allows use of the GENL_UNS_ADMIN_PERM flag on genl mcast groups
to mandate CAP_NET_ADMIN, which is important to protect token information
in the MPTCP events. This is a genetlink change.
Patch 8 adds the MPTCP netlink events.
Florian Westphal (8):
mptcp: move pm netlink work into pm_netlink
mptcp: split __mptcp_close_ssk helper
mptcp: schedule worker when subflow is closed
mptcp: move subflow close loop after sk close check
mptcp: pass subflow socket to a few helpers
mptcp: avoid lock_fast usage in accept path
genetlink: add CAP_NET_ADMIN test for multicast bind
mptcp: add netlink event support
include/net/genetlink.h | 1 +
include/uapi/linux/mptcp.h | 74 +++++++++
net/mptcp/options.c | 2 +-
net/mptcp/pm.c | 24 ++-
net/mptcp/pm_netlink.c | 310 ++++++++++++++++++++++++++++++++++++-
net/mptcp/protocol.c | 72 ++++-----
net/mptcp/protocol.h | 20 +--
net/mptcp/subflow.c | 27 +++-
net/netlink/genetlink.c | 32 ++++
9 files changed, 491 insertions(+), 71 deletions(-)
base-commit: c3ff3b02e99c691197a05556ef45f5c3dd2ed3d6
--
2.30.1
next reply other threads:[~2021-02-13 0:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 23:59 Mat Martineau [this message]
2021-02-12 23:59 ` [PATCH net-next 1/8] mptcp: move pm netlink work into pm_netlink Mat Martineau
2021-02-12 23:59 ` [PATCH net-next 2/8] mptcp: split __mptcp_close_ssk helper Mat Martineau
2021-02-12 23:59 ` [PATCH net-next 3/8] mptcp: schedule worker when subflow is closed Mat Martineau
2021-02-12 23:59 ` [PATCH net-next 4/8] mptcp: move subflow close loop after sk close check Mat Martineau
2021-02-12 23:59 ` [PATCH net-next 5/8] mptcp: pass subflow socket to a few helpers Mat Martineau
2021-02-12 23:59 ` [PATCH net-next 6/8] mptcp: avoid lock_fast usage in accept path Mat Martineau
2021-02-13 0:00 ` [PATCH net-next 8/8] mptcp: add netlink event support Mat Martineau
2021-02-13 4:46 ` [PATCH net-next 0/8] mptcp: Add genl events for connection info Mat Martineau
2021-02-13 4:52 ` Mat Martineau
2021-02-13 22:23 ` David Miller
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=20210213000001.379332-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.01.org \
--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).