mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-20 09:34:44 +08:00
d4c81bbb86
Selftests are supposed to run on any kernels, including the old ones not
supporting all MPTCP features.
At some points, a new feature caused internal behaviour changes we are
verifying in the selftests, see the Fixes tag below. It was not a uAPI
change but because in these selftests, we check some internal
behaviours, it is normal we have to adapt them from time to time after
having added some features.
It is possible to look for "mptcp_pm_subflow_check_next" in kallsyms
because it was needed to introduce the mentioned feature. So we can know
in advance what the behaviour we are expecting here instead of
supporting the two behaviours.
Link: https://github.com/multipath-tcp/mptcp_net-next/issues/368
Fixes:
|
||
|---|---|---|
| .. | ||
| .gitignore | ||
| config | ||
| diag.sh | ||
| Makefile | ||
| mptcp_connect.c | ||
| mptcp_connect.sh | ||
| mptcp_inq.c | ||
| mptcp_join.sh | ||
| mptcp_lib.sh | ||
| mptcp_sockopt.c | ||
| mptcp_sockopt.sh | ||
| pm_netlink.sh | ||
| pm_nl_ctl.c | ||
| settings | ||
| simult_flows.sh | ||
| userspace_pm.sh | ||