Searched hist:fca5c82c086ea3871b103618b80558c479c8e597 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/net/mptcp/ |
| H A D | subflow.c | diff fca5c82c086ea3871b103618b80558c479c8e597 Mon Apr 20 09:25:06 CDT 2020 Paolo Abeni <pabeni@redhat.com> mptcp: drop req socket remote_key* fields
We don't need them, as we can use the current ingress opt
data instead. Setting them in syn_recv_sock() may causes
inconsistent mptcp socket status, as per previous commit.
Fixes: cc7972ea1932 ("mptcp: parse and emit MP_CAPABLE option according to v1 spec")
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | protocol.h | diff fca5c82c086ea3871b103618b80558c479c8e597 Mon Apr 20 09:25:06 CDT 2020 Paolo Abeni <pabeni@redhat.com> mptcp: drop req socket remote_key* fields
We don't need them, as we can use the current ingress opt
data instead. Setting them in syn_recv_sock() may causes
inconsistent mptcp socket status, as per previous commit.
Fixes: cc7972ea1932 ("mptcp: parse and emit MP_CAPABLE option according to v1 spec")
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | protocol.c | diff fca5c82c086ea3871b103618b80558c479c8e597 Mon Apr 20 09:25:06 CDT 2020 Paolo Abeni <pabeni@redhat.com> mptcp: drop req socket remote_key* fields
We don't need them, as we can use the current ingress opt
data instead. Setting them in syn_recv_sock() may causes
inconsistent mptcp socket status, as per previous commit.
Fixes: cc7972ea1932 ("mptcp: parse and emit MP_CAPABLE option according to v1 spec")
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|