kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock()
authorCatalin Marinas <catalin.marinas@arm.com>
Wed, 29 Jul 2009 15:26:57 +0000 (16:26 +0100)
committerLinus Torvalds <torvalds@linux-foundation.org>
Wed, 29 Jul 2009 19:34:58 +0000 (12:34 -0700)
commitf5886c7f96f2542382d3a983c5f13e03d7fc5259
tree75c5e09bdd8726fa3fa0c2cc3b764d523e5160f2
parent84210aeb4a6a77de8a3067b121026bad630cd3da
kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock()

Objects passed to kmemleak_seq_next() have an incremented reference
count (hence not freed) but they may point via object_list.next to
other freed objects. To avoid this, the whole start/next/stop sequence
must be protected by rcu_read_lock().

Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/kmemleak.c