linux-kernel - Re: [PATCH v8 3/3] x86, mce: Add __mcsafe

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]

Date:	Mon, 11 Jan 2016 11:44:25 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Tony Luck <tony.luck@...il.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Andy Lutomirski <luto@...capital.net>,
	linux-nvdimm <linux-nvdimm@...1.01.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Robert <elliott@....com>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>, X86 ML <x86@...nel.org>
Subject: Re: [PATCH v8 3/3] x86, mce: Add __mcsafe_copy()

* Borislav Petkov <bp@...en8.de> wrote:

> On Sat, Jan 09, 2016 at 05:40:05PM -0800, Tony Luck wrote:
> > BUT ... it's all going to be very messy.  We don't have any CPUID
> > capability bits to say whether we support recovery, or which instructions
> > are good/bad choices for recovery.
> 
> We can always define synthetic ones and set them after having checked
> MCA capability bits, f/m/s, etc., maybe even based on the list you're
> supplying...

So such a synthetic CPUID bit would definitely be useful.

Also, knowing whether a memcpy function is recoverable or not, should not be 
delegated to callers: there should be the regular memcpy APIs, plus new APIs that 
do everything they can to provide recoverable memory copies. Whether it's achieved 
via flag checking, a function pointer or code patching is an implementation detail 
that's not visible to drivers making use of the new facility.

I'd go for the simplest, most robust solution initially, also perhaps with boot 
time messages to make sure users know which variant is used and now.

Thanks,

	Ingo