linux-kernel - RE: [PATCH] x86, signals: add missing signal

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] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F3A0D6A23@ORSMSX114.amr.corp.intel.com>
Date:	Tue, 24 May 2016 22:49:08 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Dave Hansen <dave@...1.net>, Ingo Molnar <mingo@...nel.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
	"bp@...en8.de" <bp@...en8.de>,
	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"x86@...nel.org" <x86@...nel.org>,
	"luto@...nel.org" <luto@...nel.org>
Subject: RE: [PATCH] x86, signals: add missing signal_compat code for x86
 features

> Tony / Borislav, do we have tests for the machine check code that could
> have caught this?

If I had built one of my recovery test programs as a 32-byte binary instead of native 64-bit I might have noticed (I only print the lsb field ... which would have been garbage on the stack, maybe I'd have spotted a silly value).

-Tony