You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Chuck Ebbert fe38d8553c [PATCH] i386 cpu hotplug: don't access freed memory ... i386 CPU init code accesses freed init memory when booting a newly-started processor after CPU hotplug. The cpu_devs array is searched to find the vendor and it contains pointers to freed data. Fix that by: 1. Zeroing entries for freed vendor data after bootup. 2. Changing Transmeta, NSC and UMC to all __init[data]. 3. Printing a warning (once only) and setting this_cpu to a safe default when the vendor is not found. This does not change behavior for AMD systems. They were broken already but no error was reported. Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		19 years ago
..
cpufreq	…
mcheck	…
mtrr	…
Makefile	…
amd.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
centaur.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
common.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
cpu.h	…
cyrix.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
intel.c	…
intel_cacheinfo.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
nexgen.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
proc.c	…
rise.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
transmeta.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago
umc.c	[PATCH] i386 cpu hotplug: don't access freed memory	19 years ago