diff options
| author | Shaohua Li <shaohua.li@intel.com> | 2005-06-25 14:55:15 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-25 16:24:34 -0700 |
| commit | ac25575203c11145066ea5cb583354cb5f0a8ade (patch) | |
| tree | f5bb286385e7a9aa0264b5186c165bac3606d327 | |
| parent | 8d783b3e02002bce8cf9d4e4a82922ee7e59b1e5 (diff) | |
| download | linux-ac25575203c11145066ea5cb583354cb5f0a8ade.tar.gz linux-ac25575203c11145066ea5cb583354cb5f0a8ade.tar.bz2 linux-ac25575203c11145066ea5cb583354cb5f0a8ade.zip | |
[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: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| -rw-r--r-- | kernel/printk.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/kernel/printk.c b/kernel/printk.c index 3a442bfb8bee..5092397fac29 100644 --- a/kernel/printk.c +++ b/kernel/printk.c @@ -588,8 +588,7 @@ asmlinkage int vprintk(const char *fmt, va_list args) log_level_unknown = 1; } - if (!cpu_online(smp_processor_id()) && - system_state != SYSTEM_RUNNING) { + if (!cpu_online(smp_processor_id())) { /* * Some console drivers may assume that per-cpu resources have * been allocated. So don't allow them to be called by this |