mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [Patch V2] x86, mce: Ensure offline CPU's don't participate in mce rendezvous process.
Date: Tue, 8 Dec 2015 10:18:13 +0100	[thread overview]
Message-ID: <20151208091812.GA27180@pd.tnic> (raw)
In-Reply-To: <20151208014142.GA82345@otc-brkl-03.jf.intel.com>

On Mon, Dec 07, 2015 at 08:41:43PM -0500, Raj, Ashok wrote:
> On Tue, Dec 08, 2015 at 12:25:24AM +0100, Borislav Petkov wrote:
> > 
> > Did you miss my statement in my previous mail where I said that the MCE
> > is being raised only on the cores of node 0?
> > 
> 
> That's right.. but i think if MCE is only given to node0, then the system 
> would panic eveytime with or without the patch. which is why i got confused.
> 
> I somehow misunderstood that with this patch the system didn't panic.

No, the system did panic in both times. The "strange" observation is
that the MCE gets reported only on the cores on node 0. Or at least only
the printks from mce_panic() on the cores on node0 reach the serial
console.

If we really broadcast only on node0, then that would be a problem if
the corrupted data leaves the node and manages to corrupt storage when
written out on some of the other nodes. I'm not sure if the kernel
panicking the whole system is on time and there's not a small window
between the detection and the panicking, in which the corruption might
happen.

If so, this'd defeat the purpose of MCE broadcasting but I'm just
hypothesizing here.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  reply	other threads:[~2015-12-08  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05  0:29 Ashok Raj
2015-12-07 20:00 ` Borislav Petkov
2015-12-07 20:04   ` Luck, Tony
2015-12-07 20:19     ` Borislav Petkov
2015-12-07 22:07       ` Luck, Tony
2015-12-07 22:34         ` Borislav Petkov
2015-12-07 23:26           ` Luck, Tony
2015-12-07 23:46           ` Raj, Ashok
2015-12-07 23:25             ` Borislav Petkov
2015-12-08  1:41               ` Raj, Ashok
2015-12-08  9:18                 ` Borislav Petkov [this message]
2015-12-08 15:59                   ` Luck, Tony
2015-12-08 18:56                     ` Borislav Petkov

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=20151208091812.GA27180@pd.tnic \
    --to=bp@alien8.de \
    --cc=ashok.raj@intel.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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

Powered by JetHome