* [PATCH 0/3] stack overflow safe kdump (2.6.18-rc1-i386)
@ 2006-07-10 7:49 Fernando Luis Vázquez Cao
0 siblings, 0 replies; only message in thread
From: Fernando Luis Vázquez Cao @ 2006-07-10 7:49 UTC (permalink / raw)
To: vgoyal; +Cc: Eric W. Biederman, akpm, ak, James.Bottomley, linux-kernel,
fastboot
Hi,
This is a the first of a series of patch-sets aiming at making kdump
more robust against stack overflows.
This patch set does the following:
* Add safe_smp_processor_id function to i386 architecture (this function
was inspired by the x86_64 function of the same name).
* Substitute "smp_processor_id" with the stack overflow-safe
"safe_smp_processor_id" in the reboot path to the second kernel.
List of patches (the last two should be applied in the order of
appearance):
[1/5] safe_smp_processor_id: stack overflow safe implementation of
smp_processor_id.
[2/5] crash_use_safe_smp_processor_id: replace smp_processor_id with
safe_smp_processor_id in "arch/i386/kernel/crash.c".
[3/5] ipi_use_safe_smp_processor_idfault: replace smp_processor_id with
safe_smp_processor_id in "include/asm-i386/mach-*/mach_ipi.h".
I tried to incorporate all the ideas received after a previous post. In
particular I hope the new code is handling the Voyager case properly.
I am looking forward to your comments and suggestions.
Regards,
Fernando
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-07-10 7:49 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-10 7:49 [PATCH 0/3] stack overflow safe kdump (2.6.18-rc1-i386) Fernando Luis Vázquez Cao
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox