public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@linux.intel.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
	tglx@linutronix.de, Yinghai Lu <yinghai@kernel.org>,
	Huang Ying <ying.huang@intel.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-tip-commits@vger.kernel.org
Subject: Re: [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit
Date: Wed, 23 Sep 2009 18:18:26 +0200	[thread overview]
Message-ID: <20090923161826.GD6105@elte.hu> (raw)
In-Reply-To: <4ABA3D31.8020507@linux.intel.com>


* Andi Kleen <ak@linux.intel.com> wrote:

> Ingo Molnar wrote:
>
>> Your sloppiness of not fixing mce_rdmsrl() as i requested brought us 
>> this new boot crash regression in 2.6.31, in mce_rdmsrl():
>
> Ingo, that's because the MSRs already have capability bits. If the 
> capability bits don't work we have to find out why, not hack around 
> without understanding it it by using rdmsrl_safe(). Most likely 
> something more is wrong then and it has to be fixed properly.

It is _entirely_ irrelevant whether, according to your opinion, this 
code 'should not crash' because there's MCE capability bits declaring 
that those MSRs should work.

Fact of life is that naked MSR reads are *dangerous*, _especially_ in 
those cases where we use a piece of functionality on a wide category of 
x86 CPUs - like in this case. They result in needless crashes when we 
have much better options, such as to print warning messages. We have 
rdmsrl_safe() for a reason and we use it in a number of critical places.

This is a very simple concept and you simply messed up on multiple 
levels here and fail to even admit to that. I even warned you about that 
very function and you ignored that. Anyway, your opinion doesnt matter 
much here, i fixed this misfeature of the MCE code already. Now we 
should get a nice warn-once boot warning (that can be picked up by 
kerneloops.org, etc.) instead of a nasty boot crash.

	Ingo

  reply	other threads:[~2009-09-23 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-4efc0670baf4b14bc95502e54a83ccf639146125@git.kernel.org>
2009-08-12 11:36 ` [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit Ingo Molnar
2009-08-17  5:00   ` Hidetoshi Seto
2009-08-17  8:35     ` Ingo Molnar
2009-08-17  9:08       ` Hidetoshi Seto
2009-08-17  9:18         ` Ingo Molnar
2009-08-17  9:20         ` Ingo Molnar
2009-08-17 11:08           ` Andi Kleen
2009-08-17 11:24             ` Ingo Molnar
2009-09-22 15:41             ` Ingo Molnar
2009-09-23 15:22               ` Andi Kleen
2009-09-23 16:18                 ` Ingo Molnar [this message]
2009-08-17 10:56         ` Andi Kleen
2009-08-17 11:00           ` Ingo Molnar
2009-08-17 11:29         ` [PATCH] x86, mce: Don't initialize MCEs on unknown CPUs Ingo Molnar
2009-08-17 11:35           ` Andi Kleen
2009-08-17 11:53             ` Ingo Molnar
2009-08-17 13:28               ` Andi Kleen
2009-08-17 11:25   ` [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit Andi Kleen

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=20090923161826.GD6105@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.com \
    --cc=yinghai@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