On 4/23/19 11:40 AM, Eric Dumazet wrote: > I believe we have a problem with f6i->rt6i_pcpu rules : > > It seems concurrent lookups can happily use it while > the call_rcu() is ongoing before fib6_info_destroy_rcu() is finally called. > > We lack proper RCU rules here. Concurrent lookups should be warned > that the destroy operation is ongoing. > > One solution could look at fib6_ref value : If it is 0, then we are > not allowed to mess with rt6i_pcpu.
ok. I'll take a look as part of the testing I am doing for other changes.
