linux-kernel - RE: [RFC] #MC mess

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F57BDDB@ORSMSX115.amr.corp.intel.com>
Date:   Tue, 18 Feb 2020 20:05:57 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Borislav Petkov <bp@...en8.de>
CC:     Peter Zijlstra <peterz@...radead.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Andy Lutomirski <luto@...nel.org>, x86-ml <x86@...nel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: RE: [RFC] #MC mess

> Yeah, ok. How do you want to select which ones? What mce_no_way_out()
> says or severity or...?

We only return from do_machine_check() in the recoverable case.  So down at the
end just here:

out_ist:
	ist_exit(regs);
}


Though that does include cases where we returned just because cfg->tolerant was
set to some value saying ignore this #MC.

-Tony