6bf41020b7
After the previous patches, the MPTCP protocol can generate fast-closes on both ends of the connection. Rework the relevant test-case to carefully trigger the fast-close code-path on a single end at the time, while ensuring than a predictable amount of data is spooled on both ends. Additionally add another test-cases for the passive socket fast-close. Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net> Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: Paolo Abeni <pabeni@redhat.com> Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile | ||
| config | ||
| diag.sh | ||
| mptcp_connect.c | ||
| mptcp_connect.sh | ||
| mptcp_inq.c | ||
| mptcp_join.sh | ||
| mptcp_sockopt.c | ||
| mptcp_sockopt.sh | ||
| pm_netlink.sh | ||
| pm_nl_ctl.c | ||
| settings | ||
| simult_flows.sh | ||
| userspace_pm.sh | ||