The patch titled
stack overflow safe kdump: safe smp_send_nmi_allbutself()
has been added to the -mm tree. Its filename is
stack-overflow-safe-kdump-safe_smp_send_nmi_allbutself.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: stack overflow safe kdump: safe smp_send_nmi_allbutself()
From: Fernando Vazquez <fernando@xxxxxxxxxxxxxxxxx>
Re-implement smp_send_nmi_allbutself() so that calls to smp_processor_id
(through send_IPI_allbutself) can be replaced with safe_smp_processor_id
without affecting other parts of the kernel (as suggested by Eric Biederman).
Signed-off-by: Fernando Vazquez <fernando@xxxxxxxxxxxxxxxxx>
Looks-reasonable-to: Andi Kleen <ak@xxxxxx>
Acked-by: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
Cc: Vivek Goyal <vgoyal@xxxxxxxxxx>
Cc: James Bottomley <James.Bottomley@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/i386/kernel/crash.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletion(-)
diff -puN arch/i386/kernel/crash.c~stack-overflow-safe-kdump-safe_smp_send_nmi_allbutself arch/i386/kernel/crash.c
--- a/arch/i386/kernel/crash.c~stack-overflow-safe-kdump-safe_smp_send_nmi_allbutself
+++ a/arch/i386/kernel/crash.c
@@ -133,7 +133,10 @@ static int crash_nmi_callback(struct not
static void smp_send_nmi_allbutself(void)
{
- send_IPI_allbutself(NMI_VECTOR);
+ cpumask_t mask = cpu_online_map;
+ cpu_clear(safe_smp_processor_id(), mask);
+ if (!cpus_empty(mask))
+ send_IPI_mask(mask, NMI_VECTOR);
}
static struct notifier_block crash_nmi_nb = {
_
Patches currently in -mm which might be from fernando@xxxxxxxxxxxxxxxxx are
stack-overflow-safe-kdump-safe_smp_processor_id.patch
stack-overflow-safe-kdump-safe_smp_processor_id_voyager.patch
stack-overflow-safe-kdump-crash_use_safe_smp_processor_id.patch
stack-overflow-safe-kdump-safe_smp_send_nmi_allbutself.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
