On 9/1/19 8:12 PM, Lorenzo Colitti wrote: > Not sure if this patch is the right fix, though, because it breaks > things in the opposite direction: even routes created by an IPv6 > address added by receiving an RA will no longer have RTF_ADDRCONF. > Perhaps add something like this as well? > > struct fib6_info *addrconf_f6i_alloc(struct net *net, struct inet6_dev *idev, > - const struct in6_addr *addr, bool > anycast, > - const struct in6_addr *addr, u8 flags, > gfp_t gfp_flags); > > flags would be RTF_ANYCAST iff the code previously called with true, > and RTF_ADDRCONF if called by a function that is adding an IPv6 > address coming from an RA.
addrconf_f6i_alloc is used for addresses added by userspace (ipv6_add_addr) and anycast. ie., from what I can see it is not used for RAs
