From: Shaohua Li <shaohua.li@intel.com>
To: akpm <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>, lkml <linux-kernel@vger.kernel.org>,
David Mosberger <davidm@napali.hpl.hp.com>
Subject: Re: Hotplug CPU printk issue
Date: Thu, 26 May 2005 13:43:31 +0800 [thread overview]
Message-ID: <1117086211.7657.10.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <20050525204828.70acc1b5.akpm@osdl.org>
On Wed, 2005-05-25 at 20:48 -0700, Andrew Morton wrote:
> > > --- a/kernel/printk.c 2005-04-12 10:12:19.000000000 +0800
> > > +++ b/kernel/printk.c 2005-04-13 17:22:40.912897328 +0800
> > > @@ -624,8 +624,7 @@ asmlinkage int vprintk(const char *fmt,
> > > 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
> > Andrew,
> > Could above patch be put into mm tree?
>
> Well not in that form. I'd appreciate being sent patches which are
> applyable rather than mangled messes, please.
>
> > It fixes the oops of CPU hotplug
> > with radeon fb enabled.
> > The reason is the per-cpu data (radeon fb calls kmalloc) isn't
> > initialized when CPU hotplug is processing. system_state is
> > SYSTEM_RUNNING for cpu hotplug.
>
> That system_state test was explicitly added by davidm a year ago:
>
> "- Allow printk on down cpus once system is running."
>
> Please confirm that we in fact do not want to allow downed CPUs to
> print things, then send a patch.
Yep. 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.
Thanks,
Shaohua
---
linux-2.6.11-rc5-mm1-root/kernel/printk.c | 3 +--
1 files changed, 1 insertion(+), 2 deletions(-)
diff -puN kernel/printk.c~printk kernel/printk.c
--- linux-2.6.11-rc5-mm1/kernel/printk.c~printk 2005-05-26 13:11:47.333540352 +0800
+++ linux-2.6.11-rc5-mm1-root/kernel/printk.c 2005-05-26 13:11:47.336539896 +0800
@@ -588,8 +588,7 @@ asmlinkage int vprintk(const char *fmt,
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
_
next prev parent reply other threads:[~2005-05-26 5:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 5:31 [PATCH 6/6]suspend/resume SMP support Li Shaohua
2005-04-12 9:43 ` Pavel Machek
2005-04-12 10:51 ` Pavel Machek
2005-04-12 12:40 ` Li Shaohua
2005-04-13 8:32 ` Pavel Machek
2005-04-14 8:27 ` Li Shaohua
2005-04-14 8:40 ` Li Shaohua
2005-04-23 22:35 ` Andrew Morton
2005-04-23 22:41 ` Pavel Machek
2005-04-25 0:49 ` Li Shaohua
2005-05-26 2:58 ` Hotplug CPU printk issue Shaohua Li
2005-05-26 3:48 ` Andrew Morton
2005-05-26 5:43 ` Shaohua Li [this message]
2005-05-26 5:52 ` Andrew Morton
2005-05-26 19:32 ` David Mosberger
2005-05-27 2:08 ` Rusty Russell
2005-04-28 7:22 ` [PATCH 6/6]suspend/resume SMP support Andrew Morton
2005-04-28 7:28 ` Li Shaohua
2005-04-28 7:41 ` Andrew Morton
2005-04-28 8:29 ` Li Shaohua
2005-04-28 8:35 ` Pavel Machek
2005-04-28 9:04 ` [ACPI] " Rafael J. Wysocki
2005-04-28 7:35 ` Li Shaohua
2005-04-28 7:42 ` Pavel Machek
2005-04-28 8:11 ` [ACPI] " Yu, Luming
2005-04-28 8:20 ` Pavel Machek
2005-04-28 8:34 ` Yu, Luming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1117086211.7657.10.camel@linux-hp.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=akpm@osdl.org \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox