The patch titled generic-ipi: fix hotplug_cfd() has been removed from the -mm tree. Its filename was generic-ipi-fix-hotplug_cfd.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: generic-ipi: fix hotplug_cfd() From: Xiao Guangrong <xiaoguangrong@xxxxxxxxxxxxxx> Use CONFIG_HOTPLUG_CPU, not CONFIG_CPU_HOTPLUG When hot-unpluging a cpu, it will leak memory allocated at cpu hotplug, but only if CPUMASK_OFFSTACK=y, which is default to n. The bug was introduced by 8969a5ede0f9e17da4b943712429aef2c9bcd82b ("generic-ipi: remove kmalloc()"). Signed-off-by: Xiao Guangrong <xiaoguangrong@xxxxxxxxxxxxxx> Cc: Ingo Molnar <mingo@xxxxxxx> Cc: Jens Axboe <jens.axboe@xxxxxxxxxx> Cc: Nick Piggin <nickpiggin@xxxxxxxxxxxx> Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx> Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx> Cc: <stable@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- kernel/smp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN kernel/smp.c~generic-ipi-fix-hotplug_cfd kernel/smp.c --- a/kernel/smp.c~generic-ipi-fix-hotplug_cfd +++ a/kernel/smp.c @@ -57,7 +57,7 @@ hotplug_cfd(struct notifier_block *nfb, return NOTIFY_BAD; break; -#ifdef CONFIG_CPU_HOTPLUG +#ifdef CONFIG_HOTPLUG_CPU case CPU_UP_CANCELED: case CPU_UP_CANCELED_FROZEN: _ Patches currently in -mm which might be from xiaoguangrong@xxxxxxxxxxxxxx are origin.patch linux-next.patch generic-ipi-make-struct-call_function_data-lockless.patch generic-ipi-make-struct-call_function_data-lockless-cleanup.patch generic-ipi-cleanup-for-generic_smp_call_function_interrupt.patch kernel-smpc-relocate-some-code.patch generic-ipi-fix-the-race-between-generic_smp_call_function_-and-hotplug_cfd.patch generic-ipi-fix-the-race-between-generic_smp_call_function_-and-hotplug_cfd-fix.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html