diff options
author | Eric Dumazet <edumazet@google.com> | 2019-05-16 05:39:52 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-05-16 22:21:00 +0300 |
commit | 61fb0d01680771f72cc9d39783fb2c122aaad51e (patch) | |
tree | 6b09b1806f97585a5259d909d0bfa47c93472d52 /net/xfrm | |
parent | 185ce5c38ea76f29b6bd9c7c8c7a5e5408834920 (diff) | |
download | linux-61fb0d01680771f72cc9d39783fb2c122aaad51e.tar.xz |
ipv6: prevent possible fib6 leaks
At ipv6 route dismantle, fib6_drop_pcpu_from() is responsible
for finding all percpu routes and set their ->from pointer
to NULL, so that fib6_ref can reach its expected value (1).
The problem right now is that other cpus can still catch the
route being deleted, since there is no rcu grace period
between the route deletion and call to fib6_drop_pcpu_from()
This can leak the fib6 and associated resources, since no
notifier will take care of removing the last reference(s).
I decided to add another boolean (fib6_destroying) instead
of reusing/renaming exception_bucket_flushed to ease stable backports,
and properly document the memory barriers used to implement this fix.
This patch has been co-developped with Wei Wang.
Fixes: 93531c674315 ("net/ipv6: separate handling of FIB entries from dst based routes")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reported-by: syzbot <syzkaller@googlegroups.com>
Cc: Wei Wang <weiwan@google.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Martin Lau <kafai@fb.com>
Acked-by: Wei Wang <weiwan@google.com>
Acked-by: Martin KaFai Lau <kafai@fb.com>
Reviewed-by: David Ahern <dsahern@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/xfrm')
0 files changed, 0 insertions, 0 deletions