diff options
author | Geliang Tang <tanggeliang@kylinos.cn> | 2025-03-07 14:21:45 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2025-03-10 23:35:48 +0300 |
commit | 7462fe22cc74321eb663768848976d42eba3ddbb (patch) | |
tree | 1a5edbf2778091bff8c2e11d0494be173fd98b6d /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 991a1b09920bc15c66f64c1e7d15cdabd3816c46 (diff) | |
download | linux-7462fe22cc74321eb663768848976d42eba3ddbb.tar.xz |
mptcp: pm: use addr entry for get_local_id
The following code in mptcp_userspace_pm_get_local_id() that assigns "skc"
to "new_entry" is not allowed in BPF if we use the same code to implement
the get_local_id() interface of a BFP path manager:
memset(&new_entry, 0, sizeof(struct mptcp_pm_addr_entry));
new_entry.addr = *skc;
new_entry.addr.id = 0;
new_entry.flags = MPTCP_PM_ADDR_FLAG_IMPLICIT;
To solve the issue, this patch moves this assignment to "new_entry" forward
to mptcp_pm_get_local_id(), and then passing "new_entry" as a parameter to
both mptcp_pm_nl_get_local_id() and mptcp_userspace_pm_get_local_id().
No behavioural changes intended.
Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20250307-net-next-mptcp-pm-reorg-v1-1-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