Re: [PATCH 09/11 net-next v5] bpf: remove ipv6_bpf_stub completely and use direct function calls

On 3/25/26 5:41 PM, Fernando Fernandez Mancera wrote:

Hi David, I did the following testing:

1. ipv6.disabled=1 since booting - the IPv6 nexthop cannot be added to
the IPv4 route at all.

2. ipv6.disabled=1 after booting but before configuring the IPv4 route -
same result as above.

3. ipv6.disabled=1 after booting and after the IPv4 is configured - the
neighbor lookup is fine as the nd_tbl is initialized. It didn't crash.

I did tracing to make sure that code path was hit. I tested the
forwarding with 3 namespaces 1<-->2<-->3 loading the BPF program on the
second one performing the bpf_fib_lookup() instruction.

I could do more testing regarding this if needed, let me know.

that looks good. Thank you