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)
committerCatalin Marinas <catalin.marinas@arm.com>
Thu, 19 May 2011 16:36:37 +0000 (17:36 +0100)
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>
Cc: <stable@kernel.org>
init/main.c

index 4a9479ef4540df99586d5e0b3854c2b3c46d91c4..48df882d51d2e709eaf5e79be55e806d75b6d6c5 100644 (file)
@@ -580,8 +580,8 @@ asmlinkage void __init start_kernel(void)
 #endif
        page_cgroup_init();
        enable_debug_pagealloc();
-       kmemleak_init();
        debug_objects_mem_init();
+       kmemleak_init();
        setup_per_cpu_pageset();
        numa_policy_init();
        if (late_time_init)