Searched hist:b6e4a1aeeb14cad595f70b31cc376903d322c821 (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/net/mptcp/ |
| H A D | protocol.c | diff b6e4a1aeeb14cad595f70b31cc376903d322c821 Fri Feb 14 16:14:29 CST 2020 Mat Martineau <mathew.j.martineau@linux.intel.com> mptcp: Protect subflow socket options before connection completes
Userspace should not be able to directly manipulate subflow socket
options before a connection is established since it is not yet known if
it will be an MPTCP subflow or a TCP fallback subflow. TCP fallback
subflows can be more directly controlled by userspace because they are
regular TCP connections, while MPTCP subflow sockets need to be
configured for the specific needs of MPTCP. Use the same logic as
sendmsg/recvmsg to ensure that socket option calls are only passed
through to known TCP fallback subflows.
Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|