public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
	"Linus Torvalds" <torvalds@transmeta.com>,
	"Olaf Zaplinski" <o.zaplinski@mediascape.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.11-pre4
Date: Fri, 05 Oct 2001 14:35:44 -0700	[thread overview]
Message-ID: <1565164462.1002292544@mbligh.des.sequent.com> (raw)
In-Reply-To: <200110052031.QAA23072@e34.esmtp.ibm.com>

> 1. OK, it fixes the UP UP_IOAPIC compilation problem.
> System (with preempt-patch) up and runnig.

Good. 
 
> 2. Woohu. I have 8 CPUs, now...;-)
> --- /proc is somewhat broken

Bugger. Didn't realise that cpu_online_map didn't get initialised
to anything sensible under UP. Should be just cosmetic (it's only
the output of /proc/cpuinfo, not the sceduler or anything), but 
try this (I haven't tested it yet - if it doesn't work, just change the
8 to 1 for a second whilst I fix it properly).

===========================

--- setup.c.old	Fri Oct  5 14:20:29 2001
+++ setup.c	Fri Oct  5 14:28:51 2001
@@ -2420,7 +2420,7 @@
 	 * WARNING - nasty evil hack ... if we print > 8, it overflows the
 	 * page buffer and corrupts memory - this needs fixing properly
 	 */
-	for (n = 0; n < 8; n++, c++) {
+	for (n = 0; n < (clustered_apic_mode ? 8 : NR_CPUS); n++, c++) {
 	/* for (n = 0; n < NR_CPUS; n++, c++) { */
 		int fpu_exception;
 #ifdef CONFIG_SMP

===========================

The reason for this hackery is that get_cpuinfo writes to a page
without proper bounds on itself. If you have more than about 8
cpus, it tramples merrily all over the next page, corrupting page
tables, etc, etc. 

The real fix for this overflow was published here a few weeks ago
by James Cleverdon (whom I work with). It's in Alan's tree, but not
Linus' as yet.

M.


       reply	other threads:[~2001-10-05 21:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200110052031.QAA23072@e34.esmtp.ibm.com>
2001-10-05 21:35 ` Martin J. Bligh [this message]
2001-10-06 20:42   ` Linux 2.4.11-pre4 Dieter Nützel
2001-10-05  4:38 Dieter Nützel
2001-10-05 16:25 ` Martin J. Bligh
2001-10-05 17:54   ` Martin J. Bligh
2001-10-05 18:15     ` Dieter Nützel
2001-10-05 20:33     ` Dieter Nützel
2001-10-05 18:11   ` Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2001-10-05  3:47 Linus Torvalds

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=1565164462.1002292544@mbligh.des.sequent.com \
    --to=martin.bligh@us.ibm.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o.zaplinski@mediascape.de \
    --cc=torvalds@transmeta.com \
    /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