Commit ac255752 authored by Shaohua Li's avatar Shaohua Li Committed by Linus Torvalds

[PATCH] CPU hotplug printk fix

In the cpu hotplug case, per-cpu data possibly isn't initialized even the
system state is 'running'.  As the comments say in the original code, some
console drivers assume per-cpu resources have been allocated.  radeon fb is
one such driver, which uses kmalloc.  After a CPU is down, the per-cpu data
of slab is freed, so the system crashed when printing some info.
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent 8d783b3e
...@@ -588,8 +588,7 @@ asmlinkage int vprintk(const char *fmt, va_list args) ...@@ -588,8 +588,7 @@ asmlinkage int vprintk(const char *fmt, va_list args)
log_level_unknown = 1; log_level_unknown = 1;
} }
if (!cpu_online(smp_processor_id()) && if (!cpu_online(smp_processor_id())) {
system_state != SYSTEM_RUNNING) {
/* /*
* Some console drivers may assume that per-cpu resources have * Some console drivers may assume that per-cpu resources have
* been allocated. So don't allow them to be called by this * been allocated. So don't allow them to be called by this
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment