From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
Alexey Dobriyan <adobriyan@gmail.com>,
Len Brown <lenb@kernel.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>, Jan Beulich <jbeulich@novell.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] fix maxcpus=1 oops in show_stat()
Date: Fri, 31 Aug 2007 04:26:50 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708310404210.4873@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070829072508.GA2707@localhost.sw.ru>
Alexey Dobriyan reports that maxcpus=1 is still broken in 2.6.23-rc4:
if CONFIG_HOTPLUG_CPU is not set, x86_64 bootup oopses in show_stat() -
for_each_possible_cpu accesses a per-cpu area which was never set up.
Alexey identified commit 61ec7567db103d537329b0db9a887db570431ff4
(ACPI: boot correctly with "nosmp" or "maxcpus=0") as the origin;
but it's not really to blame, just exposes a bug in 2.6.23-rc1's commit
8b3b295502444340dd0701855ac422fbf32e161d (Especially when !CONFIG_HOTPLUG_CPU,
avoid needlessy allocating resources for CPUs that can never become available).
rc1's test for max_cpus < 2 in start_kernel() wasn't working because
max_cpus was still NR_CPUS at that point: until rc4 moved the maxcpus
parsing earlier. Now it sets cpu_possible_map to 1 before allocating
all possible per-cpu areas; then smp_init() expands cpu_possible_map
to cpu_present_map (0xf in my case) later on.
rc1's commit has good intentions, but expects cpu_present_map to be
limited by maxcpus, which is only the case on i386. cpus_and(possible,
possible,present) might be good, but needs an audit of cpu_present_map
uses - there may well be assumptions that any cpu present is possible.
So stay safe for now and just revert those #ifndef CONFIG_HOTPLUG_CPU
optimizations in rc1's commit.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
--- 2.6.23-rc4/init/main.c 2007-08-28 04:42:58.000000000 +0100
+++ linux/init/main.c 2007-08-30 20:45:26.000000000 +0100
@@ -397,10 +397,6 @@ static void __init smp_init(void)
{
unsigned int cpu;
-#ifndef CONFIG_HOTPLUG_CPU
- cpu_possible_map = cpu_present_map;
-#endif
-
/* FIXME: This should be done in userspace --RR */
for_each_present_cpu(cpu) {
if (num_online_cpus() >= max_cpus)
@@ -545,10 +541,6 @@ asmlinkage void __init start_kernel(void
setup_arch(&command_line);
setup_command_line(command_line);
unwind_setup();
-#ifndef CONFIG_HOTPLUG_CPU
- if (max_cpus < 2)
- cpu_possible_map = cpu_online_map;
-#endif
setup_per_cpu_areas();
smp_prepare_boot_cpu(); /* arch-specific boot-cpu hooks */
next prev parent reply other threads:[~2007-08-31 3:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 11:14 2.6.23-rc4: maxcpus still broken Alexey Dobriyan
2007-08-28 23:35 ` Michal Piotrowski
2007-08-29 4:39 ` Alexey Dobriyan
2007-08-29 5:03 ` Hugh Dickins
2007-08-29 5:23 ` Alexey Dobriyan
2007-08-29 6:41 ` Len Brown
2007-08-29 7:25 ` Alexey Dobriyan
2007-08-31 3:26 ` Hugh Dickins [this message]
2007-08-31 4:33 ` [PATCH] fix maxcpus=1 oops in show_stat() Linus Torvalds
2007-08-31 7:37 ` Alexey Dobriyan
2007-08-29 20:20 ` 2.6.23-rc4: maxcpus still broken Hugh Dickins
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=Pine.LNX.4.64.0708310404210.4873@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=adobriyan@gmail.com \
--cc=adobriyan@sw.ru \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jbeulich@novell.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®