| commit | ac25575203c11145066ea5cb583354cb5f0a8ade | |
| author | Shaohua Li <shaohua.li@intel.com> | |
| Sat, 25 Jun 2005 21:55:15 +0000 (25 14:55 -0700) | ||
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | |
| Sat, 25 Jun 2005 23:24:34 +0000 (25 16:24 -0700) | ||
| tree | f5bb286385e7a9aa0264b5186c165bac3606d327 | treesnapshot (tar.gz zip) |
| parent | 8d783b3e02002bce8cf9d4e4a82922ee7e59b1e5 | commitdiff |
[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>
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>
| kernel/printk.c | diffblobblamehistory |