diff options
author | Matthieu Baerts (NGI0) <matttbe@kernel.org> | 2025-03-07 14:21:53 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2025-03-10 23:35:49 +0300 |
commit | a17336b2b2e0339b8107b9d4d0fd6b7cf51172e4 (patch) | |
tree | 7305ed5d0410563ac4b70cb8d49fff9a65a68c07 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 40aa7409d30df2b610f8e590cbb183faa2ac6f1f (diff) | |
download | linux-a17336b2b2e0339b8107b9d4d0fd6b7cf51172e4.tar.xz |
mptcp: pm: avoid calling PM specific code from core
When destroying an MPTCP socket, some userspace PM specific code was
called from mptcp_destroy_common() in protocol.c. That feels wrong, and
it is the only case.
Instead, the core now calls mptcp_pm_destroy() from pm.c which is now in
charge of cleaning the announced addresses list, and ask the different
PMs to do extra cleaning if needed, e.g. the userspace PM, if used, will
clean the local addresses list.
While at it, the userspace PM specific helper has been prefixed with
'mptcp_userspace_pm_' like the other ones.
No behavioural changes intended.
Reviewed-by: Geliang Tang <geliang@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20250307-net-next-mptcp-pm-reorg-v1-9-abef20ada03b@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions