diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2020-03-04 16:51:07 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-03-05 21:34:42 -0800 |
| commit | 2398e3991bda7caa6b112a6f650fbab92f732b91 (patch) | |
| tree | 57236049c35a02f7a728e5aa499bbd33931c9528 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | a3aefbfe45751bf7b338c181b97608e276b5bb73 (diff) | |
mptcp: always include dack if possible.
Currently passive MPTCP socket can skip including the DACK
option - if the peer sends data before accept() completes.
The above happens because the msk 'can_ack' flag is set
only after the accept() call.
Such missing DACK option may cause - as per RFC spec -
unwanted fallback to TCP.
This change addresses the issue using the key material
available in the current subflow, if any, to create a suitable
dack option when msk ack seq is not yet available.
v1 -> v2:
- adavance the generated ack after the initial MPC packet
Fixes: d22f4988ffec ("mptcp: process MP_CAPABLE data option")
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions