diff options
author | 2022-03-07 12:44:35 -0800 | |
---|---|---|
committer | 2022-03-08 22:06:11 -0800 | |
commit | 6fa0174a7c8646fce7039b5a176b4f90b0ea513a (patch) | |
tree | 190c48efc908e85f5a01b3c21b145f195959bec3 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | selftests: mptcp: Rename wait function (diff) | |
download | linux-dev-6fa0174a7c8646fce7039b5a176b4f90b0ea513a.tar.xz linux-dev-6fa0174a7c8646fce7039b5a176b4f90b0ea513a.zip |
mptcp: more careful RM_ADDR generation
The in-kernel MPTCP path manager, when processing the MPTCP_PM_CMD_FLUSH_ADDR
command, generates RM_ADDR events for each known local address. While that
is allowed by the RFC, it makes unpredictable the exact number of RM_ADDR
generated when both ends flush the PM addresses.
This change restricts the RM_ADDR generation to previously explicitly
announced addresses, and adjust the expected results in a bunch of related
self-tests.
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions