lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 23 Apr 2019 13:46:14 -0600
From:   David Ahern <>
To:     Eric Dumazet <>
Cc:     "David S . Miller" <>,
        netdev <>,
        Eric Dumazet <>,
        Wei Wang <>
Subject: Re: [PATCH net-next 1/3] ipv6: fib6_info_destroy_rcu() cleanup

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.

Powered by blists - more mailing lists