loader: investigate lost BPF complexity coverage #47647
Metadata
Metadata
Labels
Continuous Integration testing issue or flakeImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts the loading of BPF programs into the kernel.This is a bug in the Cilium logic.Relates to BPF complexity or program size issuesThis functionality worked fine before, but was broken in a newer release of Cilium.
When porting variables from macros to dynamic config variables, we've lost coverage in complexity tests. An example is the
EVENTS_MAP_RATE_LIMIT:-DEVENTS_MAP_RATE_LIMIT=1000CONFIGvariable, without adding it to the test permutations (or removing it afterwards to stay in the limit, haven't double checked). This means the respective codepath (i.e.,if (CONFIG(events_map_rate_limit) > 0)) is never verified. (occurred on this backport)This means we're potentially hitting complexity issues we're not aware of in main.