linux-kernel - RE: [git pull] machine check recovery fix

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: <3908561D78D1C84285E8C5FCA982C28F192F18E5@ORSMSX104.amr.corp.intel.com>
Date:	Fri, 18 May 2012 16:57:19 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [git pull] machine check recovery fix

> Ok, having thought it over some more, I decided to do the pull.

Thanks.

> I still think MCE is confusing and actively buggy in many respects,
> and your RIPV check is much much too late, but with your patch it's no
> worse than it used to be.

Yes, it is confusing (and buggy ... VM86 mode check needs to be added
for one thing ... the special treatment of "ip == 0" is also bad). The
lookup table in mce-severity.c is there so that you can take the ".o"
from the kernel tree and link with some user mode sanity checking
tools in the mce-test toolset. Which I think is a step up from following
the pseudo-code in the SDM (which have their own bugs).

I'll try to make it better - but it is never going to be beautiful.

-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/