summaryrefslogtreecommitdiff
path: root/net/core/sock.c
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2023-01-14 08:55:49 +0300
committerJakub Kicinski <kuba@kernel.org>2023-01-14 08:55:50 +0300
commitda263fcb86ae1ca40b5329e64ad7d7f69d260477 (patch)
tree25442684c0590cd701bd4719a23d48d6267a2266 /net/core/sock.c
parent925f3deb45df73173a33e1e81db77575f4ffde39 (diff)
parent4656d72c1efa495a58ad6d8b073a60907073e4e6 (diff)
downloadlinux-da263fcb86ae1ca40b5329e64ad7d7f69d260477.tar.xz
Merge branch 'mptcp-userspace-pm-create-sockets-for-the-right-family'
Matthieu Baerts says: ==================== mptcp: userspace pm: create sockets for the right family Before these patches, the Userspace Path Manager would allow the creation of subflows with wrong families: taking the one of the MPTCP socket instead of the provided ones and resulting in the creation of subflows with likely not the right source and/or destination IPs. It would also allow the creation of subflows between different families or not respecting v4/v6-only socket attributes. Patch 1 lets the userspace PM select the proper family to avoid creating subflows with the wrong source and/or destination addresses because the family is not the expected one. Patch 2 makes sure the userspace PM doesn't allow the userspace to create subflows for a family that is not allowed. Patch 3 validates scenarios with a mix of v4 and v6 subflows for the same MPTCP connection. These patches fix issues introduced in v5.19 when the userspace path manager has been introduced. ==================== Link: https://lore.kernel.org/r/20230112-upstream-net-20230112-netlink-v4-v6-v1-0-6a8363a221d2@tessares.net Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/core/sock.c')
0 files changed, 0 insertions, 0 deletions