fib_trie: remove potential out of bound access
authorEric Dumazet <edumazet@google.com>
Mon, 5 Aug 2013 18:18:49 +0000 (11:18 -0700)
committerBen Hutchings <ben@decadent.org.uk>
Sat, 26 Oct 2013 20:05:55 +0000 (21:05 +0100)
commitc521d041383bf06b840ee031002cf4d24d7e4673
tree7e89fae183364a638a5955dd24c5a4bac61ccd60
parent243e49a55f2b4c04e05efe3b863592b7b8b14ca2
fib_trie: remove potential out of bound access

[ Upstream commit aab515d7c32a34300312416c50314e755ea6f765 ]

AddressSanitizer [1] dynamic checker pointed a potential
out of bound access in leaf_walk_rcu()

We could allocate one more slot in tnode_new() to leave the prefetch()
in-place but it looks not worth the pain.

Bug added in commit 82cfbb008572b ("[IPV4] fib_trie: iterator recode")

[1] :
https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel

Reported-by: Andrey Konovalov <andreyknvl@google.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
net/ipv4/fib_trie.c