public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19pre3aa2
Date: Thu, 14 Mar 2002 17:13:00 +0100	[thread overview]
Message-ID: <20020314171300.H19636@suse.de> (raw)
In-Reply-To: <20020314133223.B19636@suse.de> <Pine.LNX.3.96.1020314104230.9248A-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1020314104230.9248A-100000@gatekeeper.tmr.com>; from davidsen@tmr.com on Thu, Mar 14, 2002 at 10:53:01AM -0500

On Thu, Mar 14, 2002 at 10:53:01AM -0500, Bill Davidsen wrote:
 
 >   Since vendors (and consultants) like to build a single kernel for use on
 > multiple machines, it would be nice if this could be done by some init
 > code (released) and a module. 
 
 The relevant code is (where possible) marked as __init already.
 So the init code gets thrown away whether needed or not.
 
 >   The code actually looks so small as to be unworthy of an option
 
 It's not a matter of codesize, it's a correctness issue in the source.
 #ifndef CONFIG_M686 is wrong. It assumes a P6 is the only CPU family
 in existence without the bug, despite the fact there are probably close
 to a dozen others.

 > that many people would set it off not knowing was it was much less whether
 > they needed it. This is not like a missing FPU where you can do a graceful
 > reject of the instructions, if you have the bug and not the fix you are
 > vulnerable to sudden total failures, correct?

 No. You at worse vulnerable to a malicious user running hand-crafted code
 (no compiler generates this code-sequence) bringing down the machine.

 The proposal however was not to remove anything that we currently have.
 Every kernel that is possible to be run on an affected box (i386/i486/i586)
 would still have the workaround present. We just won't generate it in
 Cyrix III, Athlon, Pentium 4, etc kernels..


-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  parent reply	other threads:[~2002-03-14 16:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  2:28 2.4.19pre3aa2 Andrea Arcangeli
2002-03-14 12:32 ` 2.4.19pre3aa2 Dave Jones
2002-03-14 12:37   ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-14 12:46   ` 2.4.19pre3aa2 Jeff Garzik
2002-03-14 12:59     ` 2.4.19pre3aa2 Dave Jones
2002-03-14 15:53   ` 2.4.19pre3aa2 Bill Davidsen
2002-03-14 16:12     ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-14 16:16       ` 2.4.19pre3aa2 Dave Jones
2002-03-14 16:32         ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-16  1:26       ` 2.4.19pre3aa2 Mike Fedyk
2002-03-14 16:13     ` Dave Jones [this message]
2002-03-14 17:16       ` 2.4.19pre3aa2 Bill Davidsen
2002-03-14 21:16   ` 2.4.19pre3aa2 H. Peter Anvin
2002-03-14 18:00 ` 2.4.19pre3aa2 Andrew Morton
2002-03-14 22:57 ` 2.4.19pre3aa2 Jari Ruusu
2002-03-15 10:56   ` 2.4.19pre3aa2 Jens Axboe
2002-03-15 11:06     ` 2.4.19pre3aa2 Jens Axboe
2002-03-15 17:35     ` 2.4.19pre3aa2 Jari Ruusu
2002-03-15 17:57       ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-16 12:10         ` 2.4.19pre3aa2 Jari Ruusu
2002-03-16 13:54           ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-18 19:13       ` 2.4.19pre3aa2 Jens Axboe
2002-03-19 23:26         ` 2.4.19pre3aa2 Jari Ruusu
2002-03-20  7:54           ` 2.4.19pre3aa2 Jens Axboe
2002-03-20 18:16             ` 2.4.19pre3aa2 Jari Ruusu
2002-03-20 14:21           ` 2.4.19pre3aa2 Herbert Valerio Riedel
2002-03-15 12:19   ` 2.4.19pre3aa2 Herbert Valerio Riedel
2002-03-15 17:36     ` 2.4.19pre3aa2 Jari Ruusu
2002-03-15 18:36       ` 2.4.19pre3aa2 Herbert Valerio Riedel
2002-03-16 12:12         ` 2.4.19pre3aa2 Jari Ruusu

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=20020314171300.H19636@suse.de \
    --to=davej@suse.de \
    --cc=andrea@suse.de \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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