mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Max Asbock <masbock@linux.vnet.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Should corrected machine check errors still taint the kernel?
Date: Tue, 29 Mar 2011 20:06:06 -0700	[thread overview]
Message-ID: <20110330030606.GA2427@alboin.amr.corp.intel.com> (raw)
In-Reply-To: <1301443098.5867.34.camel@w-amax.beaverton.ibm.com>

On Tue, Mar 29, 2011 at 04:58:17PM -0700, Max Asbock wrote:
> I noticed that corrected machine check errors taint the kernel. And it
> looks like they have done that forever.
> 
> Is that still the right thing to do?

Likely not.

> 
> The comment in add_taint() says:
> "Can't trust the integrity of the kernel anymore."

The comment is definitely wrong agreed. 

-Andi

      reply	other threads:[~2011-03-30  3:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 23:58 Max Asbock
2011-03-30  3:06 ` Andi Kleen [this message]

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=20110330030606.GA2427@alboin.amr.corp.intel.com \
    --to=ak@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masbock@linux.vnet.ibm.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

all inboxes | Powered by JetHome®