On Fri, Mar 22, 2019 at 8:48 AM Willem de Bruijn <[email protected]> wrote: > > On Fri, Mar 22, 2019 at 11:44 AM Alexei Starovoitov > <[email protected]> wrote: > > > > On Fri, Mar 22, 2019 at 8:15 AM Willem de Bruijn > > <[email protected]> wrote: > > > > > > +#define BPF_F_ADJ_ROOM_ENCAP_L3_IPV4 (1ULL << 1) > > > +#define BPF_F_ADJ_ROOM_ENCAP_L3_IPV6 (1ULL << 2) > > > +#define BPF_F_ADJ_ROOM_ENCAP_L3_MASK (BPF_F_ADJ_ROOM_ENCAP_L3_IPV4 | \ > > > + BPF_F_ADJ_ROOM_ENCAP_L3_IPV6) > > > > mask is still in uapi... > > That's only the L3 MASK, which captures ipv4 or ipv6. I don't see that > being expanded.
and what's the use of it for user space? packet is either ipv4 or ipv6. passing two flags will be rejected: if (flags & BPF_F_ADJ_ROOM_ENCAP_L3_IPV4 && + flags & BPF_F_ADJ_ROOM_ENCAP_L3_IPV6) + return -EINVAL;
