kmemleak: Initialise kmemleak after debug_objects_mem_init()
authorCatalin Marinas <catalin.marinas@arm.com>
Thu, 19 May 2011 15:25:30 +0000 (16:25 +0100)
committerSteve Conklin <sconklin@canonical.com>
Fri, 15 Jul 2011 17:20:45 +0000 (12:20 -0500)
commitc4a85535be441af016e6475cd786536c4e9179eb
treebb75f3b5575d767934dff662f4c0a1834df766a9
parent2cc4b72d85dcec389db444a19580ff0600161a2f
kmemleak: Initialise kmemleak after debug_objects_mem_init()

BugLink: http://bugs.launchpad.net/bugs/793702

commit 9b090f2da85bd0df5e1a1ecfe4120b7b50358f48 upstream.

Kmemleak frees objects via RCU and when CONFIG_DEBUG_OBJECTS_RCU_HEAD
is enabled, the RCU callback triggers a call to free_object() in
lib/debugobjects.c. Since kmemleak is initialised before debug objects
initialisation, it may result in a kernel panic during booting. This
patch moves the kmemleak_init() call after debug_objects_mem_init().

Reported-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Tested-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
init/main.c