Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bpf: nodeport: fix up trace point in to-overlay NAT paths #24886

Merged
merged 1 commit into from
Apr 18, 2023
Merged

bpf: nodeport: fix up trace point in to-overlay NAT paths #24886

merged 1 commit into from
Apr 18, 2023

Commits on Apr 14, 2023

  1. bpf: nodeport: fix up trace point in to-overlay NAT paths 

    We have a number of cases (EgressGW, DSR-GENEVE) where the to-overlay
program is used even when the cluster is in native routing mode.

But the trace points inside handle_nat_fwd() currently only report
TRACE_TO_OVERLAY iff called from IS_BPF_OVERLAY *and* routing-mode=tunnel.
Thus when in native routing mode, we get misleading trace notifications
from inside to-overlay that report TRACE_TO_NETWORK.

Fix this by only checking for IS_BPF_OVERLAY when selecting the obs_point.

Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
    @julianwiedmann
    julianwiedmann committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    be819cf View commit details
    Browse the repository at this point in the history